Virtual world processing device and method

ABSTRACT

A virtual world processing apparatus and method. Sensed information, which is information collected by a sensor is inputted. The sensed information is adapted, based on a sensor capability, which is information on capability of the sensor. Accordingly, interoperability between a real world and a virtual world or interoperability between virtual worlds may be achieved.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a national phase application, under 35 U.S.C. 371,of International Application No. PCT/KR2010/004091, filed Jun. 23, 2010,which claimed priority to Korean Application No. 10-2009-0057313, filedJun. 25, 2009, Korean Application No. 10-2009-0101434, filed Oct. 23,2009, Korean Application No. 10-2009-0104474, filed Oct. 30, 2009,Korean Application No. 10-2010-0003607, filed Jan. 14, 2010, KoreanApplication No. 10-2010-0006119, filed Jan. 22, 2010 and U.S.Provisional Application No. 61/255,636 filed Oct. 28, 2009, thedisclosures of which are incorporated herein by reference.

BACKGROUND

1. Field

Example embodiments of the following description relate to a method andapparatus for processing a virtual world, and more particularly, to amethod and apparatus for applying information of a real world to avirtual world.

2. Description of the Related Art

Currently, an interest in experience-type games has been increasing.MICROSOFT CORPORATION introduced “Project Natal” at the “E3 2009” PressConference. “Project Natal” may provide a user body motion capturingfunction, a face recognition function, and a voice recognition functionby combining MICROSOFT's XBOX 360 game console with a separate sensordevice consisting of a depth/color camera and a microphone array,thereby enabling a user to interact with a virtual world without adedicated controller. In addition, SONY CORPORATION introduced “Wand”which is an experience-type game motion controller. The “Wand” enablesinteraction with a virtual world through input of a motion trajectory ofa controller by applying, to the PLAYSTATION 3 game console, alocation/direction sensing technology obtained by combining a colorcamera, a marker, and an ultrasonic sensor.

The interaction between a real world and a virtual world has twodirections. In one direction, data information obtained by a sensor ofthe real world may be reflected to the virtual world. In the otherdirection, data information, obtained from the virtual world may bereflected to the real world using an actuator. Embodiments suggest avirtual world processing apparatus and method to apply informationobtained through the sensor of the real world to the virtual world inorder to achieve the interaction between the real world and the virtualworld.

SUMMARY

Additional aspects and/or advantages will be set forth in part in thedescription which follows and, in part, will be apparent from thedescription, or may be learned by practice of the invention.

According to example embodiments, there is provided a virtual worldprocessing apparatus to enable interoperability between a virtual worldand a real world or interoperability between virtual worlds, theapparatus including an input unit to be inputted with sensed informationcollected by a sensor from the real world, and an adapting unit to adaptthe sensed information, based on sensor capability related to thesensor.

According to example embodiments, sensed information which isinformation collected by a sensor is inputted. The sensed information isadapted, based on a sensor capability, which is information oncapability of the sensor. Accordingly, interoperability between a realworld and a virtual world or interoperability between virtual worlds maybe achieved.

BRIEF DESCRIPTION OF THE DRAWINGS

These and/or other aspects and advantages will become apparent and morereadily appreciated from the following description of the embodiments,taken in conjunction with the accompanying drawings of which:

FIG. 1 is a view illustrating an operation of manipulating an object ofa virtual world using a sensor according to example embodiments;

FIG. 2 is a view illustrating a system for manipulating an object of avirtual world using a sensor, according to example embodiments;

FIG. 3 is a view illustrating a system for manipulating an object of avirtual world using a sensor, according to other example embodiments;

FIG. 4 is a view illustrating a structure of a virtual world processingapparatus, according to example embodiments;

FIG. 5 is a view illustrating a structure of a virtual world processingapparatus, according to other example embodiments;

FIG. 6 is a view illustrating a structure of a virtual world processingapparatus, according to still other example embodiments;

FIG. 7 is a view illustrating a sensor capability base type, accordingto example embodiments;

FIG. 8 is a view illustrating syntax of a sensor capability base type,according to example embodiments;

FIG. 9 is a view illustrating syntax of sensor capability baseattributes, according to example embodiments;

FIG. 10 is a view illustrating a sensor adaptation preference base type,according to example embodiments;

FIG. 11 is a view illustrating syntax of a sensor adaptation preferencebase type, according to example embodiments;

FIG. 12 is a view illustrating syntax of sensor adaptation preferencebase attributes, according to example embodiments;

FIG. 13 is a view illustrating a sensed information base type, accordingto example embodiments;

FIG. 14 is a flowchart illustrating a virtual world processing method,according to example embodiments;

FIG. 15 is a view illustrating a flowchart of a virtual world processingmethod, according to other example embodiments; and

FIG. 16 is a view illustrating an operation of using a virtual worldprocessing apparatus, according to example embodiments.

DETAILED DESCRIPTION

Reference will now be made in detail to example embodiments, examples ofwhich are illustrated in the accompanying drawings, wherein likereference numerals refer to the like elements throughout. Exampleembodiments are described below in order to explain example embodimentsby referring to the figures.

Hereinafter, the example embodiments will be described with reference tothe accompanying drawings.

FIG. 1 illustrates an operation of manipulating a virtual world object120 of a virtual world, using a sensor 100, according to exampleembodiments.

Referring to FIG. 1, a user 110 of a real world may manipulate thevirtual world object 120 of the virtual world using the sensor 100. Theuser 110 may input his or her motion, state, intention, shape, and thelike, through the sensor 100. The sensor 100 may transmit controlinformation (CI) related to the motion, state, intention, shape, and thelike, of the user 110, the CI included in a sensor signal, to a virtualworld processing apparatus.

The virtual world may be classified into a virtual environment and avirtual world object. The virtual world object may be classified into anavatar and a virtual object.

Depending on embodiments, the user 110 of the real world may includehumans, animals, plants, inanimate objects, and even environmentalconditions of the user 110, such as, temperature and atmosphericpressure.

FIG. 2 illustrates a system for manipulating a virtual world using asensor, according to example embodiments.

Referring to FIG. 2, the signal that includes CI 201, related to themotion, state, intention, shape, and the like, of a user of a real world210, is inputted through a sensor as a real world device, and may betransmitted to a virtual world processing apparatus. Depending onembodiments, the CI 201 related to the motion, state, intention, shape,and the like, of the user may include a sensor capability, a sensoradaptation preference, and sensed information, which will be describedin detail with reference to FIG. 7 through FIG. 16.

The virtual world processing apparatus may include an adaptation of thereal world to the virtual world (RV) 220. The adaptation RV 220 may beimplemented by an RV engine. The adaptation RV 220 may convertinformation of the real world 210 to information applicable to a virtualworld 240, using the CI 201 related to the motion, state, intention,shape, and the like, of the user of the real world 210, the CI 201included in the sensor signal.

Depending on embodiments, the adaptation RV 220 may convert virtualworld information (VWI) 202 using the CI 201 related to the motion,state, shape, and the like of the user of the real world 210.

The VWI 202 denotes information on the virtual world 240. For example,the VWI 202 may include information on an object of the virtual world240 or elements constituting the object.

The virtual world processing apparatus may transmit convertedinformation 203 converted by the adaptation RV 220 to the virtual world240 through an adaptation real world to virtual world/virtual world toreal world (RV/VR) 230.

Table 1 illustrates structures shown in FIG. 2.

TABLE 1 SIDC Sensory input device VWI Virtual world capabilities.information Another expression of sensor capability USIP User sensoryinput SODC Sensory output device preferences. capabilities Anotherexpression of sensor adaptation preference SIDCmd Sensory input deviceUSOP User sensory output commands preferences Another expression ofsensed information VWC Virtual world SODCmd Sensory output devicecapabilities commands VWP Virtual world SEM Sensory effect metadatapreferences VWEM Virtual world effect SI Sensory information metadata

FIG. 3 illustrates a system for manipulating an object of a virtualworld 265 using a sensor 250, according to other example embodiments.

Referring to FIG. 3, the sensor 250 may collect information on a motion,state, intention, shape, and the like, of a user of a real world.

The sensor 250 may include a metadata encoder 251 configured to encodethe information collected by the sensor 250 into metadata.

The metadata encoder 251 may encode the information collected by thesensor 250 to first metadata. The sensor 250 may transmit the firstmetadata to an adaptation RV 255.

A metadata decoder 256 included in the adaptation RV 255 may decode thefirst metadata received from the sensor 250. In addition, a metadatadecoder 258 included in the adaptation RV 255 may decode second metadatareceived from an adaptation VR 260.

The second metadata may be metadata encoded from information on thevirtual world 265 by a metadata encoder 257 included in the adaptationVR 260.

The adaptation RV 255 may generate information to be applied to thevirtual world 265, based on information decoded from the first metadataby the metadata decoder 256 and information decoded from the secondmetadata by the metadata decoder 258. Here, the adaptation RV 255 maygenerate the information to be applied to the virtual world 265, suchthat the information corresponds to virtual world object characteristicsand sensed information included in the second metadata.

The metadata encoder 257 may encode the information, which is generatedby the adaptation RV 255 and to be applied to the virtual world 265,into third metadata. In addition, the adaptation RV 255 may transmit thethird metadata to the adaptation VR 260.

A metadata decoder 271 included in the adaptation VR 260 may decode thethird metadata. The adaptation VR 260 may convert attributes of theobject of the virtual world 265, based on the decoded information and,in addition, apply the converted attributes to the virtual world 265.

FIG. 4 illustrates a structure of a virtual world processing apparatus300, according to example embodiments.

Referring to FIG. 4, the virtual world processing apparatus 300 includesa storage unit 310 and a processing unit 320.

The storage unit 310 stores a sensor capability describing capability ofa sensor.

The sensor is a device for measuring a motion, state, intention, shape,and the like, of a user of a real world. The sensor may be expressed asa sensory input device. Depending on embodiments, the sensor may beclassified according to sensor types including (1) acoustic, sound, andvibration, (2) automotive and transportation, (3) chemical, (4) electriccurrent, electric potential, magnetic, and radio, (5) environment andweather, (6) flow, (7) ionizing radiation, and subatomic particles, (8)navigation instruments, (9) position, angle, displacement, distance,speed, and acceleration, (10) optical, light, and imaging, (11)pressure, force, density, and level, (12) thermal, heat, andtemperature, (13) proximity and presence, and (14) sensor technology.

Table 2 illustrates example sensors according to the sensor types. Thesensors in Table 2 are suggested only as an embodiment but not limiting.

TABLE 2 sensor type list of sensors (1) acoustic, sound, geophonevibration hydrophone lace sensor, a guitar pickup microphone seismometeraccelerometer (2) automotive, crank sensor transportation curb feelerdefect detector map sensor parking sensors parktronic radar gunspeedometer speed sensor throttle position sensor variable reluctancesensor wheel speed sensor (3) chemical breathalyzer carbon dioxidesensor carbon monoxide detector catalytic bead sensor chemicalfield-effect transistor electronic noseelectrolyte-insulator-semiconductor sensor hydrogen sensor infraredpoint sensor ion-selective electrode nondispersive infrared sensormicrowave chemistry sensor nitrogen oxide sensor optode oxygen sensorpellistor pH glass electrode potentiometric sensor redox electrode smokedetector zinc oxide nanorod sensor (4) electric current, ammeterelectric potential, current sensor magnetic, radio galvanometer halleffect sensor hall probe leaf electroscope magnetic anomaly detectormagnetometer metal detector multimeter ohmmeter voltmeter watt-hourmeter (5) environment, fish counter weather gas detector hygrometerpyranometer pyrgeometer rain gauge rain sensor seismometers (6) flow airflow meter flow sensor gas meter mass flow sensor water meter (7)ionizing radiation, bubble chamber subatomic particles cloud chambergeiger counter neutron detection particle detector scintillation counterscintillator wire chamber (8) navigation air speed indicator instrumentsaltimeter attitude indicator fluxgate compass gyroscope inertialreference unit magnetic compass MHD sensor ring laser gyroscope turncoordinator variometer vibrating structure gyroscope yaw rate sensor (9)position, angle, accelerometer displacement, inclinometer distance,speed, laser rangefinder acceleration linear encoder linear variabledifferential transformer (LVDT) liquid capacitive inclinometers odometerpiezoelectric accelerometer position sensor rotary encoder rotaryvariable differential transformer selsyn tachometer (10) optical, light,charge-coupled device imaging colorimeter infra-red sensor LED as lightsensor nichols radiometer fiber optic sensors photodiode photomultipliertubes phototransistor photoelectric sensor photoionization detectorphotomultiplier photoresistor photoswitch phototube proximity sensorscintillometer shack-Hartmann wavefront sensor (11) pressure, force,anemometer density, level bhangmeter barograph barometer hydrometerLevel sensor Load cell magnetic level gauge oscillating U-tube pressuresensor piezoelectric sensor pressure gauge strain gauge torque sensorviscometer (12) thermal, heat, bolometer temperature calorimeter heatflux sensor infrared thermometer microbolometer microwave radiometer netradiometer resistance temperature detector resistance thermometerthermistor thermocouple thermometer (13) proximity, alarm sensorpresence bedwetting alarm motion detector occupancy sensor passiveinfrared sensor reed switch stud finder triangulation sensor touchswitch wired glove (14) sensor active pixel sensor technology machinevision biochip biosensor capacitance probe catadioptric sensor carbonpaste electrode displacement receiver electromechanical filmelectro-optical sensor image sensor inductive sensor intelligent sensorlab-on-a-chip leaf sensor RADAR sensor array sensor node soft sensorstaring array transducer ultrasonic sensor video sensor

For example, the microphone belonging to a sensor type (1) acoustic,sound, and vibration may collect voice of the user of the real world andambient sounds of the user. The speed sensor belonging to the sensortype (2) automotive and transportation may measure speed of the user ofthe real world and speed of an object, such as, a vehicle of the realworld. The oxygen sensor belonging to the sensor type (3) chemical maymeasure an oxygen ratio in ambient air around the user of the real worldand an oxygen ratio in liquid around the user of the real world. Themetal detector belonging to the sensor type (4) electric current,electric potential, magnetic, and radio may detect metallic substancespresent in or around the user of the real world. The rain sensorbelonging to the sensor type (5) environment and weather may detectwhether it is raining in the real world. The flow sensor belonging tothe sensor type (6) flow may measure a ratio of a fluid flow of the realworld. The scintillator belonging to the sensor type (7) ionizingradiation and subatomic particles may measure a ratio or radiationpresent in or around the user of the real world. The variometerbelonging to the sensor type (8) navigation instruments may measure avertical movement speed of or around the user of the real world. Theodometer belonging to the sensor type (9) position, angle, displacement,distance, speed, and acceleration may measure a traveling distance of anobject of the real world, such as a vehicle. The phototransistorbelonging to the sensor type (10) optical, light, and imaging maymeasure light of the real world. The barometer belonging to the sensortype (11) pressure, force, density, and level may measure an atmosphericpressure of the real world. The bolometer belonging to the sensor type(12) thermal, heat, and temperature may measure radiation rays of thereal world. The motion detector belonging to the sensor type (13)proximity and presence may measure a motion of the user of the realworld. The biosensor belonging to the sensor type (14) may measurebiological characteristics of the user of the real world.

FIG. 5 illustrates a structure of a virtual world processing apparatus,according to other example embodiments.

Referring to FIG. 5, an input device 360 according to the presentembodiments may be input with a sensor adaptation preference 361 by auser of a real world. Depending on embodiments, the input device 360 maybe modularized and inserted in a sensor 370 or a virtual worldprocessing apparatus 350. The sensor adaptation preference 361 will bedescribed in further detail with reference to FIGS. 10 to 12.

The sensor 370 may transmit a sensor capability 371 and sensedinformation 372 to the virtual world processing apparatus 350. Thesensor capability 371 and the sensed information 372 will be describedin further detail with reference to FIGS. 7 to 9 and 13.

The virtual world processing apparatus 350 may include a signalprocessing unit 351 and an adaptation unit 352.

The signal processing unit 351 may receive the sensor capability 371 andthe sensed information 372, and perform signal-processing with respectto the sensor capability 371 and the sensed information 372. Dependingon embodiments, the signal processing unit 351 may filter and validatethe sensor capability 371 and the sensed information 372.

The adaptation unit 352 may receive the sensor adaptation preference 361from the input device 360. In addition, based on the received sensoradaptation preference 361, the adaptation unit 352 may performadaptation with respect to the information signal-processed by thesignal processing unit 351 so that the information is applied to avirtual world 380. In addition, the virtual world processing apparatus350 may apply the information having undergone the adaptation by theadaptation unit 352 to the virtual world 380.

The sensor capability 371 denotes information on capability of a sensor.

A sensor capability base type denotes a base type of the sensorcapability. Depending on embodiments, the sensor capability base typemay be a base abstract type of the metadata related to a sensorcapability commonly applied to all types of sensors, as part of metadatatypes related to the sensor capability.

Hereinafter, the sensor capability 371 and the sensor capability basetype will be described in detail with reference to FIGS. 7 to 9.

FIG. 7 illustrates a sensor capability base type 400, according toexample embodiments.

Referring to FIG. 7, the sensor capability base 400 may include sensorcapability base attributes 410 and any attributes 420.

The sensor capability base attributes 410 denote a group of sensorcapabilities basically included in the sensor capability base type 400.

The any attributes 420 denote a group of additional sensor capabilitiesof a sensor. The any attributes 420 may be unique additional sensorcapabilities, which are applicable to an arbitrary sensor. The anyattributes 420 may allow scalability for inclusion of attributes otherthan the base attributes.

FIG. 8 illustrates syntax 500 of a sensor capability base type accordingto example embodiments.

Referring to FIG. 8, the syntax 500 of the sensor capability base typemay include a diagram 510, attributes 520, and a source 530.

The diagram 510 may include a diagram of the sensor capability basetype.

The attributes 520 may include sensor capability base attributes and anyattributes.

The source 530 may include a program representing the sensor capabilitybase type using an extensible markup language (XML). However, the source530 shown in FIG. 8 is suggested by way of example but not limiting.

FIG. 9 illustrates syntax 600 of sensor capability base attributes,according to example embodiments.

Referring to FIG. 9, the syntax 600 of the sensor capability baseattributes may include a diagram 610, attributes 620, and a source 630.

The diagram 610 may include a diagram of the sensor capability baseattributes.

The attributes 620 may include a unit 601, a maximum value 602, aminimum value 603, an offset 604, a number of levels 605, a sensitivity606, a signal to noise ratio (SNR) 607, and an accuracy 608.

The unit 601 is a unit of values measured by a sensor. Depending onembodiments, for example, when the sensor is a thermometer, the unit 601may be Celsius (° C.) and Fahrenheit (° F.). When the sensor is a speedsensor, the unit 601 may be kilometers per hour (km/h) and meters persecond (m/s).

The maximum value 602 and the minimum value 603 denote a maximum valueand a minimum value measurable by the sensor, respectively. Depending onembodiments, for example, when the sensor is a thermometer, the maximumvalue 602 may be 50° C. and the minimum value 603 may be 0° C. Even inthe same type of sensor, for example, the thermometer, the maximum value602 and the minimum value 603 may be varied, according to use andfunction of the sensor.

The offset 604 denotes a value added to a value measured by the sensorto obtain an absolute value. Depending on embodiments, for example,presuming that the sensor is a speed sensor and a user or an object of areal world stays still, when a value other than zero is measured asspeed, the sensor may determine the offset 604 to a value making thespeed zero. For example, when −1 km/h is measured as speed of a vehicleof the real world, the offset 604 may be 1 km/h.

The number of levels 605 denotes a number of values measurable by thesensor. That is, the number of levels 605 represents the number ofvalues between the maximum value and the minimum value measured by thesensor. Depending on embodiments, for example, presuming that the sensoris a thermometer and the maximum value and the minimum value are 50° C.and 0° C., respectively, when the number of levels 605 is 5, the sensormay measure five values, that is, 10° C., 20° C., 30° C., 40° C., and50° C. Even when temperature of the real world is 27° C., not only when20° C., the temperature may be measured as 20° C. through round-down.Alternative, in this case, the temperature may be measured as 30° C.through roundup.

The sensitivity 606 denotes a minimum input value required for thesensor to measure an output value. That is, the sensitivity 606 maydenote a minimum input signal value for generation of the output signal.Depending on embodiments, for example, when the sensor is a thermometerand the sensitivity 606 is 1° C., the sensor may not measure atemperature change less than 1° C. but measure only the temperaturechange of at least 1° C.

The SNR 607 denotes a relative degree of a signal measured by the sensorwith respect to a noise. Depending on embodiments, presuming that thesensor is a microphone to measure and a vocal sound of the user of thereal world is to be measured, when an ambient noise is large, the SNR607 of the sensor may be relatively small.

The accuracy 608 denotes an error of the sensor. That is, the accuracy608 denotes a degree of closeness of a measured quantity with respect toan actual value. Depending on embodiments, when the sensor is amicrophone, the accuracy 608 may be a measurement error caused byvariation of a propagation speed of a sound according to temperature,humidity, and the like. Alternatively, the accuracy 608 may bedetermined through a statistical error of the values already measured bythe sensor.

Depending on embodiments, the attributes 620 may further include aposition. The position denotes a position of the sensor. When the sensoris a thermometer, the position of the sensor may be an armpit of theuser of the real world. The position may include longitude and latitude,and height and direction from a ground surface.

The unit 601, the maximum value 602, the minimum value 603, the offset604, the number of levels 605, the sensitivity 606, the SNR 607, theaccuracy 608, and the position, as the sensor capability baseattributes, may be rearranged as shown in Table 3.

TABLE 3 Name Definition Unit 601 The unit of value maxValue The maximumvalue that the input device (sensor) can 602 provide. The terms will bedifferent according to the individual device type. minValue The minimumvalue that the input device (sensor) can 603 provide. The terms will bedifferent according to the individual device type. Offset 604 The numberof value locations added to a base value in order to get to a specificabsolute value. numOflevels The number of value levels that the devicecan provide 605 in between maximum and minimum value. Sensitivity Theminimum magnitude of input signal required to 606 produce a specifiedoutput signal. SNR 607 The ratio of a signal power to the noise powercorrupting the signal Accuracy The degree of closeness of a measuredquantity to its 608 actual value Position The position of the devicefrom the user's perspective according to the x-, y-, and z-axis

The source 630 may include a program representing the sensor capabilitybase attributes using the XML.

A reference numeral 631 of the source 630 defines the maximum value 602using the XML. According to the reference numeral 631, the maximum value602 has “float” type data and is optionally used.

A reference numeral 632 of the source 630 defines the minimum value 603using the XML. According to the reference numeral 632, the minimum value603 has “float” type data and is optionally used.

A reference numeral 633 of the source 630 defines the number of levels605 using the XML. According to the reference numeral 633, the number oflevels 605 has “on NegativeInteger” type data and is optionally used.

However, the source 630 shown in FIG. 9 is not limiting but only exampleembodiments.

Referring to FIG. 4 again, the processing unit 320 may determine a firstvalue received from the sensor based on the sensor capability, andtransmit a second value corresponding to the first value to the virtualworld.

Depending on embodiments, the processing unit 320 may transmit thesecond value to the virtual world when the first value received from thesensor is less than or equal to a maximum value measurable by the sensorand greater than or equal to a minimum value measurable by the sensor.

Depending on embodiments, when the first value received from the sensoris greater than the maximum value, the processing unit 320 may considerthe first value as the maximum value and transmit the second value tothe virtual world. In addition, when the first value is less than theminimum value, the processing unit 320 may consider the first value asthe minimum value and transmit the second value to the virtual world.

The virtual world processing apparatus 300 may further include a secondstorage unit (not shown) configured to store a sensor adaptationpreference for manipulation of the first value received from the sensor.The processing unit 320 may generate a third value from the first valuebased on the sensor capability, and generate the second value from thethird value based on the sensor adaptation preference.

Depending on embodiments, information on the motion, state, intention,shape, and the like of the user of the real world, which are measuredthrough the sensor, may be directly reflected to the virtual world.

FIG. 6 illustrates a structure of a virtual world processing apparatus390 according to still other example embodiments.

Referring to FIG. 6, the virtual world processing apparatus 390 isconfigured to enable interoperability between a virtual world and a realworld or interoperability between virtual worlds. The virtual worldprocessing apparatus 390 may include an input unit 391 and an adaptingunit 392.

The input unit 391 may be input with sensed information collected by asensor from the real world.

The input unit 391 may be further input with a sensor adaptationpreference for manipulation of the sensed information. The sensoradaptation preference will be described in further detail with referenceto FIGS. 10 to 12.

The adapting unit 392 may adapt the sensed information input to theinput unit 391, based on the sensor capability.

For example, when a speed sensor sensed speed of the user of the realworld and collected the sensed information of 30 m/s, the input unit 391may be input with the sensed information of 30 m/s. Here, when a maximumvalue of the sensor capability related to the speed sensor is 20 m/s,the adapting unit 392 may adapt the sensed information of 30 m/s to 20m/s. In addition, the virtual world processing apparatus may apply theadapted sensed information of 20 m/s to the virtual world.

Depending on embodiments, the sensor capability may be input and storedin advance in the virtual world processing apparatus. The sensorcapability may be input through the input unit 391.

The adapting unit 392 may adapt the sensed information based on thesensor adaptation preference.

The virtual world processing apparatus 390 may further include an outputunit 393.

The output unit 393 may output the sensed information to control thevirtual world. Depending on embodiments, the output unit 393 may outputthe sensed information adapted based on the sensor capability.Furthermore, the output unit 393 may output the sensed informationadapted based on the sensor capability and the sensor adaptationpreference.

An output unit 393 according to other example embodiments may output thesensed information to control virtual world object information whichdenotes information on an object implemented in the virtual world.Depending on embodiments, the output unit 393 may output the sensedinformation adapted based on the sensor capability. Furthermore, theoutput unit 393 may output the sensed information adapted based on thesensor capability and the sensor adaptation preference.

Hereinafter, the sensor capability will be described in relation tospecific embodiments of the sensor. Although not limited to thoseembodiments, the sensor may include a position sensor, an orientationsensor, an acceleration sensor, a light sensor, a sound sensor, atemperature sensor, a humidity sensor, a length sensor, a motion sensor,an intelligent camera sensor, an ambient noise sensor, an atmosphericsensor, a velocity sensor, an angular velocity sensor, an angularacceleration sensor, a force sensor, a torque sensor, and a pressuresensor.

Source 1 denotes a sensor capability related to the position sensorusing the XML. However, a program source shown in Source 1 is only anexample embodiment and does not limit the present disclosure.

[Source 1] <!-- ################################################ --><!-- Position Sensor capability type     --> <!--################################################ --> <complexTypename=“PositionSensorCapabilityType”> <complexContent> <extensionbase=“cid:SensorCapabilityBaseType”> <sequence> <element name=“range”type=“cid:RangeType”/> </sequence> </extension> </complexContent></complexType> <complexType name=“RangeType”> <sequence> <elementname=“XminValue” type=“float”/> <element name=“XmaxValue” type=“float”/><element name=“YminValue” type=“float”/> <element name=“YmaxValue”type=“float”/> <element name=“ZminValue” type=“float”/> <elementname=“ZmaxValue” type=“float”/> </sequence> </complexType>

A position sensor capability type is a tool for describing the sensorcapability related to the position sensor.

The position sensor capability type may include sensor capability baseattributes related to the position sensor.

The sensor capability base attributes related to the position sensor mayinclude a range, a range type, an x maximum value, an x minimum value, ay maximum value, a y minimum value, a z maximum value, and a z minimumvalue.

The range denotes a range measurable by the position sensor. Forexample, the measurable range of the position sensor may be expressedusing the range type and a global coordinate system.

An origin of the global coordinate may be located at a top left cornerof a screen. A right handed coordinate system may be applied as theglobal coordinate. In the global coordinate, a positive direction of anx-axis may be a direction to a top right corner of the screen, apositive direction of a y-axis may be a gravity direction, that is, abottomward direction of the screen, and a positive direction of a z-axismay be a direction opposite to the user, that is, a direction into thescreen.

The range type denotes a range of the global coordinate system accordingto the x-axis, the y-axis, and the z-axis.

The x maximum value denotes a maximum value on the x-axis, measurable bythe position sensor using a unit of a position coordinate, for example,a meter.

The x minimum value denotes a minimum value on the x-axis, measurable bythe position sensor using a unit of a position coordinate, for example,a meter.

The y maximum value denotes a maximum value on the y-axis, measurable bythe position sensor using a unit of a position coordinate, for example,a meter.

The y minimum value denotes a minimum value on the y-axis, measurable bythe position sensor using a unit of a position coordinate, for example,a meter.

The z maximum value denotes a maximum value on the z-axis, measurable bythe position sensor using a unit of a position coordinate, for example,a meter.

The z minimum value denotes a minimum value on the z-axis, measurable bythe position sensor using a unit of a position coordinate, for example,a meter.

Source 2 denotes a sensor capability related to an orientation sensorusing the XML. However, a program source shown in Source 2 is only anexample embodiment and does not limit the present disclosure.

[Source 2] <!-- ################################################ --><!-- Orientation Sensor capability type     --> <!--################################################ --> <complexTypename=“OrientationSensorCapabilityType”> <complexContent> <extensionbase=“cid:SensorCapabilityBaseType”> <sequence> <elementname=“orientationrange” type=“cid:OrientationRangeType”/> </sequence></extension> </complexContent> </complexType> <complexTypename=“OrientationRangeType”> <sequence> <element name=“XMinRotation”type=“float”/> <element name=“XMaxRotation” type=“float”/> <elementname=“YMinRotation” type=“float”/> <element name=“YMaxRotation”type=“float”/> <element name=“ZMinRotation” type=“float”/> <elementname=“ZMaxRotation” type=“float”/> </sequence> </complexType>

An orientation sensor capability type is a tool for describing thesensor capability related to the orientation sensor.

The orientation sensor capability type may include sensor capabilitybase attributes related to the orientation sensor.

The sensor capability base attributes related to the orientation sensormay include an orientation range, an orientation range type, an xmaximum value, an x minimum value, a y maximum value, a y minimum value,a z maximum value, and a z minimum value.

The range denotes a range measurable by the orientation sensor. Forexample, the measurable range of the orientation sensor may be expressedusing the orientation range type and the global coordinate system.

The orientation range type denotes an orientation range of the globalcoordinate system, according to the x-axis, the y-axis, and the z-axis.

The x maximum value denotes a maximum value on the x-axis, measurable bythe orientation sensor using a unit of an orientation coordinate, forexample, a radian.

Similarly, the x minimum value denotes a minimum value on the x-axis,measurable by the orientation sensor using a unit of an orientationcoordinate, for example, a radian.

The y maximum value denotes a maximum value on the y-axis, measurable bythe orientation sensor using a unit of an orientation coordinate, forexample, a radian.

The y minimum value denotes a minimum value on the y-axis, measurable bythe orientation sensor using a unit of an orientation coordinate, forexample, a radian.

The z maximum value denotes a maximum value on the z-axis, measurable bythe orientation sensor using a unit of an orientation coordinate, forexample, a radian.

The z minimum value denotes a minimum value on the z-axis, measurable bythe orientation sensor using a unit of an orientation coordinate, forexample, a radian.

Source 3 denotes a sensor capability related to an acceleration sensorusing the XML. However, a program source shown in Source 3 is only anexample embodiment and does not limit the present disclosure.

[Source 3] <!-- ################################################ --><!-- Acceleration Sensor capability type     --> <!--################################################ --> <complexTypename=“AccelerationSensorCapabilityType”> <complexContent> <extensionbase=“cid:SensorCapabilityBaseType”> </extension> </complexContent></complexType>

An acceleration sensor capability type is a tool for describing thesensor capability related to the acceleration sensor.

The acceleration sensor capability type may include sensor capabilitybase attributes related to the acceleration sensor.

The sensor capability base attributes related to the acceleration sensormay include a maximum value and a minimum value.

The maximum value denotes a maximum value measurable by the accelerationsensor using a unit of acceleration, for example, m/s².

Similarly, the minimum value denotes a minimum value measurable by theacceleration sensor using a unit of acceleration, for example, m/s².

Source 4 denotes a sensor capability related to a light sensor using theXML. However, a program source shown in Source 4 is only an exampleembodiment and does not limit the present disclosure.

[Source 4] <!-- ################################################ --><!-- Light Sensor capability type     --> <!--################################################ --> <complexTypename=“LightSensorCapabilityType”> <complexContent> <extensionbase=“cid:SensorCapabilityBaseType”> <sequence> <element name=“color”type=“cid:colorType” minOccurs=“0” maxOccurs=“unbounded”/> </sequence><attribute name=“location” type=“mpeg7:termReferenceType”use=“optional”/> </extension> </complexContent> </complexType>

A light sensor capability type is a tool for describing the sensorcapability related to the light sensor.

The light sensor capability type may include sensor capability baseattributes related to the light sensor.

The sensor capability base attributes related to the light sensor mayinclude a maximum value, a minimum value, a color, and a location.

The maximum value denotes a maximum value measurable by the light sensorusing a unit of light intensity, for example, LUX.

Likewise, the minimum value denotes a minimum value measurable by thelight sensor using a unit of light intensity, for example, LUX.

The color denotes a color that may be provided by the light sensor. Forexample, the color may be an RGB color value.

The location denotes a location of the light sensor. For example, thelocation of the light sensor may be expressed using the globalcoordinate according to the x-axis, the y-axis, and the z-axis.

Source 5 denotes a sensor capability related to a sound sensor using theXML. However, a program source shown in Source 5 is only an exampleembodiment and does not limit the present disclosure.

[Source 5] <!--######################## --> <!-- Sound Sensor capabilitytype --> <!--######################## --> <complexTypename=“SoundSensorCapabilityType”>  <complexContent>   <extensionbase=“sidc:CapabilityBaseType”/>  </complexContent> </complexType>

A sound sensor capability type is a tool for describing the sensorcapability related to the sound sensor.

The sound sensor capability type may include sensor capability baseattributes related to the sound sensor.

The sensor capability base attributes related to the sound sensor mayinclude a maximum value and a minimum value.

The maximum value denotes a maximum value measurable by the sound sensorusing a unit of sound intensity, for example, a decibel (dB).

Similarly, the minimum value denotes a minimum value measurable by thesound sensor using a unit of sound intensity, for example, a dB.

Source 6 denotes a sensor capability related to a temperature sensorusing the XML. However, a program source shown in Source 6 is only anexample embodiment and does not limit the present disclosure.

[Source 6] <!-- ################################################ --><!-- Temperature Sensor capability type     --> <!--################################################ --> <complexTypename=“TemperatureSensorCapabilityType”> <complexContent> <extensionbase=“cid:SensorCapabilityBaseType”> <attribute name=“location”type=“mpeg7:termReferenceType” use=“optional”/>  </extension></complexContent> </complexType>

A temperature sensor capability type is a tool for describing the sensorcapability related to the temperature sensor.

The temperature sensor capability type may include sensor capabilitybase attributes related to the temperature sensor.

The sensor capability base attributes related to the temperature sensormay include a maximum value, a minimum value, and a location.

The maximum value denotes a maximum value measurable by the temperaturesensor using a unit of temperature, for example, ° C. and ° F.

The minimum value denotes a minimum value measurable by the temperaturesensor using a unit of temperature, for example, ° C. and ° F.

The location denotes a location of the temperature sensor. For example,the location of the temperature sensor may be expressed using the globalcoordinate according to the x-axis, the y-axis, and the z-axis.

Source 7 denotes a sensor capability related to a humidity sensor usingthe XML. However, a program source shown in Source 7 is only an exampleembodiment and does not limit the present disclosure.

[Source 7] <!-- ################################################ --><!-- Humidity Sensor capability type     --> <!--################################################ --> <complexTypename=“HumiditySensorCapabilityType”> <complexContent> <extensionbase=“cid:SensorCapabilityBaseType”> <attribute name=“location”type=“mpeg7:termReferenceType” use=“optional”/>  </extension></complexContent> </complexType>

A humidity sensor capability type is a tool for describing the sensorcapability related to the humidity sensor.

The humidity sensor capability type may include sensor capability baseattributes related to the humidity sensor.

The humidity capability base attributes related to the humidity sensormay include a maximum value, a minimum value, and a location.

The maximum value denotes a maximum value measurable by the humiditysensor using a unit of humidity, for example, percent (%).

The minimum value denotes a minimum value measurable by the humiditysensor using a unit of humidity, for example, %.

The location denotes a location of the humidity sensor. For example, thelocation of the humidity sensor may be expressed using the globalcoordinate according to the x-axis, the y-axis, and the z-axis.

Source 8 denotes a sensor capability related to a length sensor usingthe XML. However, a program source shown in Source 8 is only an exampleembodiment and does not limit the present disclosure.

[Source 8] <!-- ################################################ --><!-- Length Sensor capability type     --> <!--################################################ --> <complexTypename=“LengthSensorCapabilityType”> <complexContent> <extensionbase=“cid:SensorCapabilityBaseType”> <attribute name=“location”type=“mpeg7:termReferenceType” use=“optional”/>  </extension></complexContent> </complexType>

A length sensor capability type is a tool for describing the sensorcapability related to the length sensor.

The length sensor capability type may include sensor capability baseattributes related to the length sensor.

The length capability base attributes related to the length sensor mayinclude a maximum value, a minimum value, and a location.

The maximum value denotes a maximum value measurable by the lengthsensor using a unit of length, for example, a meter.

Similarly, the minimum value denotes a minimum value measurable by thelength sensor using a unit of length, for example, a meter.

The location denotes a location of the length sensor. For example, thelocation of the length sensor may be expressed using the globalcoordinate according to the x-axis, the y-axis, and the z-axis.

Source 9 denotes a sensor capability related to a motion sensor usingthe XML. However, a program source shown in Source 9 is only an exampleembodiment and does not limit the present disclosure.

[Source 9] <!-- ################################################ --><!-- Motion Sensor capability type     --> <!--################################################ --> <complexTypename=“MotionSensorCapabilityType”>   <sequence>     <elementname=“positioncapability” type=“cid:PositionSensorCapabilityType”minOccurs=“0”/>     <element name=“orientationcapability”type=“cid:OrientationSensorCapabilityType” minOccurs=“0”/>     <elementname=“velocitycapability” type=“cid:VelocitySensorCapabilityType”minOccurs=“0”/>     <element name=“angularvelocitycapability”type=“cid:AngularVelocitySensorCapabilityType” minOccurs=“0”/>    <element name=“accelerationrange”type=“cid:AccelerationSensorCapabilityType” minOccurs=“0”/>     <elementname=“angularaccelerationcapability”type=“cid:AngularAccelerationSensorCapabilityType” minOccurs=“0”/>  </sequence> </complexType>

A motion sensor capability type is a tool for describing the sensorcapability related to the motion sensor.

The motion sensor may be an integrated sensor of a plurality of sensors.For example, the motion sensor may integrally include a position sensor,a velocity sensor, an acceleration sensor, an orientation sensor, anangular velocity sensor, and an angular acceleration sensor.

The motion sensor capability type may include sensor capability baseattributes related to the motion sensor.

The sensor capability base attributes related to the motion sensor mayinclude a position capability, a velocity capability, an accelerationcapability, an orientation capability, an angular velocity capability,and an angular acceleration capability.

The position capability denotes capability with respect to the position.

The velocity capability denotes capability with respect to the velocity.

The acceleration capability denotes capability with respect to theacceleration.

The orientation capability denotes capability with respect to theorientation.

The angular velocity capability denotes capability with respect to theangular velocity.

The angular acceleration capability denotes capability with respect tothe angular acceleration.

For example, Source 10 denotes a sensor capability related to anintelligent camera sensor using the XML. However, a program source shownin Source 10 is only an example embodiment and does not limit thepresent disclosure.

[Source 10] <!-- ################################################ --><!-- Intelligent Camera CapabilityType     --> <!--################################################ --> <complexTypename=“IntelligentCameraCapabilityType”>   <complexContent>    <extension base=“cid:SensorCapabilityBaseType”>       <sequence>        <element name=“FeatureTrackingStatus” type=“boolean”minOccurs=“0”/>         <element name=“FacialExpressionTrackingStatus”type=“boolean” minOccurs=“0”/>         <elementname=“GestureTrackingStatus” type=“boolean”minOccurs=“0”/>         <element name=“maxBodyFeaturePoint” type=“float”minOccurs=“0”/>         <element name=“maxFaceFeaturePoint” type=“float”minOccurs=“0”/>         <element name=“TrackedFeature”type=“cid:FeatureType”/>         <elementname=“TrackedFacialFeaturePoints” type=“cid:FacialFeatureMask”/>        <element name=“TrackedBodyFeaturePoints”type=“cid:BodyFeatureMask”/>       </sequence>     </extension>  </complexContent> </complexType> <complexType name=“FeatureType”>  <sequence>     <element name=“Face” type=“boolean”/>     <elementname=“Body” type=“boolean”/>     <element name=“Both” type=“boolean”/>  </sequence> </complexType> <complexType name=“FacialFeatureMask”>  <sequence>     <element name=“FaceFeaturePoint” type=“boolean”minOccurs=“60” maxOccurs=“200”/>   </sequence> </complexType><complexType name=“BodyFeatureMask”>   <sequence>     <elementname=“BodyFeaturePoint” type=“boolean” minOccurs=“60” maxOccurs=“200”/>  </sequence> </complexType>

An intelligent camera sensor capability type is a tool for describingthe sensor capability related to the intelligent camera sensor.

The intelligent camera sensor capability type may include sensorcapability base attributes related to the intelligent camera sensor.

The sensor capability base attributes related to the intelligent camerasensor may include a feature tracking status, an expression trackingstatus, a body movement tracking status, a maximum body feature point, amaximum face feature point, a tracked feature, tracked facial featurepoints, tracked body feature points, a feature type, a facial featuremask, and a body feature mask.

The feature tracking status denotes information on whether anintelligent camera is capable of tracking features.

The expression tracking status denotes information on whether theintelligent camera is capable of extracting animation related to afacial expression.

The body movement tracking status denotes information on whether theintelligent camera is capable of extracting animation related to a body.

The maximum body feature point denotes a maximum value of a body featurethat can be tracked by the intelligent camera sensor.

The maximum face feature point denotes a maximum value of a face featurethat can be tracked by the intelligent camera sensor.

The tracked feature denotes information on whether tracking of the bodyfeature and the face feature is possible.

The tracked facial feature points denote information on whether therespective face features are activated or based on the facial featuremask.

The tracked body feature points denote information on whether therespective body features are activated or based on the body featuremask.

The feature type denotes a list of feature types. For example, thefeature type may include a face, a body, and both face and body.

The facial feature mask denotes a list of facial features.

The body feature mask denotes a list of body features.

Source 11 denotes a sensor capability related to an ambient noise sensorusing the XML. However, a program source shown in Source 11 is only anexample embodiment and does not limit the present disclosure.

[Source 11] <!-- ################################################ --><!-- Ambient noise Sensor capability type     --> <!--################################################ --> <complexTypename=“AmbientNoiseSensorCapabilityType”> <complexContent> <extensionbase=“cid:SensorCapabilityBaseType”> <attribute name=“location”type=“mpeg7:termReferenceType” use=“optional”/>  </extension></complexContent> </complexType>

An ambient noise sensor capability type is a tool for describing thesensor capability related to the ambient noise sensor.

The ambient noise sensor capability type may include sensor capabilitybase attributes related to the ambient noise sensor.

The sensor capability base attributes related to the ambient noisesensor may include a maximum value, a minimum value, and a location.

The maximum value denotes a maximum value measurable by the ambientnoise sensor. For example, a unit for the ambient noise sensor may bedB.

The minimum value denotes a minimum value measurable by the ambientnoise sensor. For example, a unit for the ambient noise sensor may bedB.

The location denotes a location of the ambient noise sensor. Forexample, the location of the ambient noise sensor may be expressed usingthe global coordinate according to the x-axis, the y-axis, and thez-axis.

Source 12 denotes a sensor capability related to an atmospheric pressuresensor using the XML. However, a program source shown in Source 12 isonly an example embodiment and does not limit the present disclosure.

[Source 12] <!-- ################################################ --><!-- Atmospheric Pressure Sensor capability type     --> <!--################################################ --> <complexTypename=“AtmosphericPressureSensorCapabilityType”> <complexContent><extension base=“cid:SensorCapabilityBaseType”> <attributename=“location” type=“mpeg7:termReferenceType” use=“optional”/> </extension> </complexContent> </complexType>

An atmospheric pressure sensor capability type is a tool for describingthe sensor capability related to the atmospheric pressure sensor.

The atmospheric pressure sensor capability type may include sensorcapability base attributes related to the atmospheric pressure sensor.

The atmospheric pressure capability base attributes related to theatmospheric pressure sensor may include a maximum value, a minimumvalue, and a location.

The maximum value denotes a maximum value measurable by the atmosphericpressure sensor using a unit of atmospheric pressure, for example, ahectopascal (hPa).

Similarly, the minimum value denotes a minimum value measurable by theatmospheric pressure sensor using a unit of atmospheric pressure, forexample, a hPa.

The location denotes a location of the atmospheric pressure sensor. Forexample, the location of the atmospheric pressure sensor may beexpressed using the global coordinate according to the x-axis, they-axis, and the z-axis.

Source 13 denotes a sensor capability related to a velocity sensor usingthe XML. However, a program source shown in Source 13 is only an exampleembodiment and does not limit the present disclosure.

[Source 13] <!-- ################################################ --><!-- Velocity Sensor capabilitytype    --> <!--################################################ --> <complexTypename=“VelocitySensorCapabilityType”> <complexContent> <extensionbase=“cid:SensorCapabilityBaseType”> </extension> </complexContent></complexType>

A velocity sensor capability type is a tool for describing the sensorcapability related to the velocity sensor.

The velocity sensor capability type may include sensor capability baseattributes related to the velocity sensor.

The velocity capability base attributes related to the velocity sensormay include a maximum value and a minimum value.

The maximum value denotes a maximum value measurable by the velocitysensor using a unit of velocity, for example, m/s.

The minimum value denotes a minimum value measurable by the velocitysensor using a unit of velocity, for example, m/s.

Source 14 denotes a sensor capability related to an angular velocitysensor using the XML. However, a program source shown in Source 14 isonly an example embodiment and does not limit the present disclosure.

[Source 14] <!-- ################################################ --><!-- Angular Velocity Sensor capabilitytype    --> <!--################################################ --> <complexTypename=“AngularVelocitySensorCapabilityType”> <complexContent> <extensionbase=“cid:SensorCapabilityBaseType”> </extension> </complexContent></complexType>

An angular velocity sensor capability type is a tool for describing thesensor capability related to the angular velocity sensor.

The angular velocity sensor capability type may include sensorcapability base attributes related to the angular velocity sensor.

The angular velocity capability base attributes related to the angularvelocity sensor may include a maximum value and a minimum value.

The maximum value denotes a maximum value measurable by the angularvelocity sensor using a unit of angular velocity, for example,radians/s.

The minimum value denotes a minimum value measurable by the angularvelocity sensor using a unit of angular velocity, for example,radians/s.

Source 15 denotes a sensor capability related to an angular accelerationsensor using the XML. However, a program source shown in Source 15 isonly an example embodiment and does not limit the present disclosure.

[Source 15] <!-- ################################################ --><!-- Angular Acceleration Sensor capabilitytype    --> <!--################################################ --> <complexTypename=“AngularAccelerationSensorCapabilityType”> <complexContent><extension base=“cid:SensorCapabilityBaseType”> </extension></complexContent> </complexType>

An angular acceleration sensor capability type is a tool for describingthe sensor capability related to the angular acceleration sensor.

The angular acceleration sensor capability type may include sensorcapability base attributes related to the angular acceleration sensor.

The angular acceleration capability base attributes related to theangular acceleration sensor may include a maximum value and a minimumvalue.

The maximum value denotes a maximum value measurable by the angularacceleration sensor using a unit of angular acceleration, for example,radians/s².

The minimum value denotes a minimum value measurable by the angularacceleration sensor using a unit of angular acceleration, for example,radians/s².

Source 16 denotes a sensor capability related to a force sensor usingthe XML. However, a program source shown in Source 16 is only an exampleembodiment and does not limit the present disclosure.

[Source 16] <!-- ################################################ --><!-- Force Sensor capability type    --> <!--################################################ --> <complexTypename=“ForceSensorCapabilityType”> <complexContent> <extensionbase=“cid:SensorCapabilityBaseType”> </extension> </complexContent></complexType>

A force sensor capability type is a tool for describing the sensorcapability related to the force sensor.

The force sensor capability type may include sensor capability baseattributes related to the force sensor.

The force capability base attributes related to the force sensor mayinclude a maximum value and a minimum value.

The maximum value denotes a maximum value measurable by the force sensorusing a unit of force, for example, a Newton (N).

The minimum value denotes a minimum value measurable by the force sensorusing a unit of force, for example, a N.

Source 17 denotes a sensor capability related to a torque sensor usingthe XML. However, a program source shown in Source 17 is only an exampleembodiment and does not limit the present disclosure.

[Source 17] <!-- ################################################ --><!-- Torque Sensor capability type    --> <!--################################################ --> <complexTypename=“ForceSensorCapabilityType”> <complexContent> <extensionbase=“cid:SensorCapabilityBaseType”> </extension> </complexContent></complexType>

A torque sensor capability type is a tool for describing the sensorcapability related to the torque sensor.

The torque sensor capability type may include sensor capability baseattributes related to the torque sensor.

The torque capability base attributes related to the torque sensor mayinclude a maximum value, a minimum value, and a location.

The maximum value denotes a maximum value measurable by the torquesensor using a unit of torque, for example, a Newton millimeter (N-mm).

The minimum value denotes a minimum value measurable by the torquesensor using a unit of torque, for example, a N-mm.

Source 18 denotes a sensor capability related to a pressure sensor usingthe XML. However, a program source shown in Source 18 is only an exampleembodiment and does not limit the present disclosure.

[Source 18] <!-- ################################################ --><!-- Pressure Sensor capability type    --> <!--################################################ --> <complexTypename=“PressureSensorCapabilityType”> <complexContent> <extensionbase=“cid:SensorCapabilityBaseType”> </extension> </complexContent></complexType>

A pressure sensor capability type is a tool for describing the sensorcapability related to the pressure sensor.

The pressure sensor capability type may include sensor capability baseattributes related to the pressure sensor.

The pressure capability base attributes related to the pressure sensormay include a maximum value, a minimum value, and a location.

The maximum value denotes a maximum value measurable by the pressuresensor using a unit of pressure, for example, a Pascal (Pa), Atmosphere(atm), PSI, Torr, or any other unit of pressure.

The minimum value denotes a minimum value measurable by the pressuresensor using a unit of pressure, for example, a Pa, atm, PSI, Torr, orany other unit of pressure.

Hereinafter, the sensor adaptation preference will be described indetail.

The sensor adaptation preference denotes information for manipulating avalue received from a sensor. That is, the sensor adaptation preferencemay denote information on preference of a user with respect to a methodof adapting sensed information collected from the sensor.

A sensor adaptation preference base type denotes a base type ofmanipulation information of the user. Depending on embodiments, thesensor adaptation preference base type may be a base abstract type ofthe metadata related to a sensor adaptation preference commonly appliedto all types of sensors, as part of metadata types related to the sensoradaptation preference.

Hereinafter, the sensor adaptation preference and the sensor adaptationpreference base type will be described in detail with reference to FIGS.10 through 12.

FIG. 10 illustrates a sensor adaptation preference base type 700according to example embodiments.

Referring to FIG. 10, the sensor adaptation preference base type 700 mayinclude sensor adaptation preference base attributes 710 and anyattributes 720.

The sensor adaptation preference base attributes 710 denote a group ofsensor adaptation preferences basically included in the sensoradaptation preference base type 700.

The any attributes 720 denote a group of additional sensor adaptationpreferences. The any attributes 720 may be unique additional sensorcapabilities which are applicable to an arbitrary sensor. The anyattributes 420 may allow scalability for inclusion of attributes otherthan the base attributes.

FIG. 11 illustrates syntax 800 of a sensor adaptation preference basetype according to example embodiments.

Referring to FIG. 11, the syntax of the sensor adaptation preferencebase type may include a diagram 810, attributes 820, and a source 830.

The diagram 810 may include a diagram of the sensor adaptationpreference base type.

The attributes 820 may include sensor adaptation preference baseattributes and any attributes.

The source 830 may include a program representing the sensor adaptationpreference base type using an XML. However, the source 830 shown in FIG.11 is suggested by way of example and is not limiting.

FIG. 12 illustrates syntax 900 of sensor adaptation preference baseattributes according to example embodiments.

Referring to FIG. 12, the syntax 900 of the sensor adaptation preferencebase attributes may include a diagram 910, attributes 920, and a source930.

The diagram 910 may include a diagram of the sensor adaptationpreference base attributes.

The attributes 920 may include a sensor identifier (ID) reference 901, asensor adaptation mode 902, an activation state 903, a unit 904, amaximum value 905, a minimum value 906, and a number of levels 907.

The sensor ID reference 901 denotes information referencing an ID of anindividual sensor that generates specific sensed information.

The sensor adaptation mode 902 denotes user preference informationrelated to a method of adapting a sensor. Depending on embodiments, thesensor adaptation mode 902 may be a sensor adaptation preference relatedto an adaptation method that refines information on a motion, state,intention, shape, and the like of a user of a real world, measuredthrough the sensor, and reflects the information to a virtual world. Forexample, a ‘strict’ value may denote a user preference that directlyapplies sensed information of the real world to the virtual world. A‘scalable’ value may denote a user preference that varies the sensedinformation of the real world according to the user preference andapplies the sensed information to the virtual world.

The activation state information 903 denotes information on whether toactivate the sensor in the virtual world. Depending on embodiments, theactivation state information 903 may be a sensor adaptation preferencethat determines whether the sensor is in operation.

The unit 904 denotes a unit of a value used in the virtual world. Forexample, the unit 904 may be a pixel. In addition, the unit 904 may be aunit of a value corresponding to the value received from the sensor.

The maximum value 905 and the minimum value 906 denote a maximum valueand a minimum value used in the virtual world, respectively. Dependingon embodiments, the maximum value 905 and the minimum value 906 may bethe unit of the value corresponding to the value received from thesensor.

The number of levels 907 denotes a number of levels used in the virtualworld. Depending on embodiments, the number of levels 907 may be a valuefor dividing levels between the maximum value and the minimum used inthe virtual world.

The sensor ID reference 901, the adaptation mode 902, the activationstate 903, the unit 904, the maximum value 905, the minimum value 906,and the number of levels 907, as the sensor adaptation preference baseattributes, may be rearranged as shown in Table 4.

TABLE 4 Name Definition SensorIdRef Refers the ID of an individualsensor that has generated 901 the specific sensed information Sensor Theuser's preference on the adaptation method for the adaptation virtualworld effect mode 902 Activate 903 Whether the effect shall beactivated. A value of true means the effect shall be activated and falsemeans the effect shall be deactivated Unit 904 The unit of valuemaxValue 905 The maximum desirable value of the effect in percentageaccording to the max scale defined within the semantics definition ofthe individual effects minValue 906 The minimum desirable value of theeffect in percentage according to the min scale defined within thesemantics definition of the individual effects numOflevels The number ofvalue levels that the device can provide 907 in between maximum andminimum value

The source 930 may include a program representing the sensor adaptationpreference base attributes using the XML.

For example, a reference numeral 931 defines the activation state 903using the XML. According to the reference numeral 931, the activationstate 903 has “boolean” type data and is optionally used.

As another example, a reference numeral 932 defines the maximum value905 using the XML. According to the reference numeral 932 the maximumvalue 905 has “float” type data and is optionally used.

As another example, a reference number 933 defines minimum value 906using the XML. According to the reference numeral 933, the minimum value906 has “float” type data and is optionally used.

As another example, a reference numeral 934 defines the number of levels907 using the XML. According to the reference numeral 934, the number oflevels 907 has “onNegativeInteger” type data and is optionally used.

However, the source 930 illustrated in FIG. 12 is only an exampleembodiment, and thus, is not limiting.

Hereinafter, the sensor adaptation preference will be described inrelation to specific embodiments of the sensor.

Source 19 denotes a sensor adaptation preference related to a positionsensor using the XML. However, a program source shown in Source 19 isonly an example embodiment and does not limit the present disclosure.

[Source 19] <!-- ################################################ --><!-Position Sensor Preference type    --> <!--################################################ --> <complexTypename=“PositionSensorPrefType”> <complexContent> <extensionbase=“cid:SensorCapabilityBaseType”> <sequence> <element name=“range”type=“cid:RangeType”/> </sequence> </extension> </complexContent></complexType>

A position sensor type is a tool for describing the sensor adaptationpreference related to the position sensor.

A position sensor capability type may include sensor adaptationpreference base attributes related to the position sensor.

The sensor adaptation preference base attributes related to the positionsensor may include a range and a number of levels.

The range denotes a range of a user preference with respect to positioninformation measured by the position sensor.

The number of levels denotes a number of levels of the user preferencewith respect to the position information measured by the positionsensor.

Source 20 denotes a sensor adaptation preference related to anorientation sensor using the XML. However, a program source shown inSource 20 is only an example embodiment and does not limit the presentdisclosure.

[Source 20] <!-- ################################################ --><!-- Orientation Sensor Preference type    --> <!--################################################ --> <complexTypename=“OrientationSensorPrefType”> <complexContent> <extensionbase=cid:SensorCapabilityBaseType/> <sequence> <elementname=“orientationrange” type=“cid:OrientationRangeType”/> </sequence></extension> </complexContent> </complexType>

An orientation sensor type is a tool for describing the sensoradaptation preference related to the orientation sensor.

An orientation sensor capability type may include sensor adaptationpreference base attributes related to the orientation sensor.

The sensor adaptation preference base attributes related to theorientation sensor may include an orientation range and a number oflevels.

The orientation range denotes a range of a user preference with respectto orientation information measured by the orientation sensor.

The number of levels denotes a number of levels of the user preferencewith respect to the orientation information measured by the orientationsensor.

Source 21 denotes a sensor adaptation preference related to anacceleration sensor using the XML. However, a program source shown inSource 21 is only an example embodiment and does not limit the presentdisclosure.

[Source 21] <!-- ################################################ --><!-- Acceleration Sensor Preference type    --> <!--################################################ --> <complexTypename=“AccelerationSensorPrefType”> <complexContent> <extensionbase=cid:SensorCapabilityBaseType/> </complexContent> </complexType>

An acceleration sensor type is a tool for describing the sensoradaptation preference related to the acceleration sensor.

An acceleration sensor capability type may include sensor adaptationpreference base attributes related to the acceleration sensor.

The sensor adaptation preference base attributes related to theacceleration sensor may include a maximum value, a minimum value, and anumber of levels.

The maximum value denotes a maximum value of a user preference relatedto acceleration information measured by the acceleration sensor.

The minimum value denotes a minimum value of the user preference relatedto the acceleration information measured by the acceleration sensor.

The number of levels denotes a number of levels of the user preferencewith respect to the acceleration information measured by theacceleration sensor.

Source 22 denotes a sensor adaptation preference related to a lightsensor using the XML. However, a program source shown in Source 22 isonly an example embodiment and does not limit the present disclosure.

[Source 22] <!-- ################################################ --><!-- Light Sensor Preference type    --> <!--################################################ --> <complexTypename=“LightSensorPrefType”> <complexContent> <extensionbase=“cid:UserSensorPreferenceBaseType”> <sequence> <elementname=“color” type=“cid:colorType” minOccurs=“0” maxOccurs=“unbounded”/></sequence> </extension> </complexContent> </complexType>

A light sensor type is a tool for describing the sensor adaptationpreference related to the light sensor.

A light sensor capability type may include sensor adaptation preferencebase attributes related to the light sensor.

The sensor adaptation preference base attributes related to the lightsensor may include a maximum value, a minimum value, a number of levels,and an unfavorable color.

The maximum value denotes a maximum value of a user preference relatedto a value measured by the light sensor.

The minimum value denotes a minimum value of the user preference relatedto a value measured by the light sensor.

The number of levels denotes a number of levels of the user preferencewith respect to a value measured by the light sensor.

The unfavorable color denotes a list of unfavorable colors of the user,as RGB color values or a classification reference.

Source 23 denotes a sensor adaptation preference related to a soundsensor using the XML. However, a program source shown in Source 23 isonly an example embodiment and does not limit the present disclosure.

[Source 23] <!--######################## --> <!-- USIPV Sound Sensortype  --> <!--######################## --> <complexTypename=“SoundSensorType”>  <complexContent>   <extensionbase=“usip:PreferenceBaseType”/>  </complexContent> </complexType>

A sound sensor type is a tool for describing the sensor adaptationpreference related to the sound sensor.

A sound sensor capability type may include sensor adaptation preferencebase attributes related to the sound sensor.

The sensor adaptation preference base attributes related to the soundsensor may include a maximum value and a minimum value.

The maximum value denotes a maximum value allowed by the user as ameasured value of the sound sensor.

The minimum value denotes a minimum value allowed by the user as ameasured value of the sound sensor.

Source 24 denotes a sensor adaptation preference related to atemperature sensor using the XML. However, a program source shown inSource 24 is only an example embodiment and does not limit the presentdisclosure.

[Source 24] <!-- ################################################ --><!-- Temperature Sensor Preference type    --> <!--################################################ --> <complexTypename=“TemperatureSensorPrefType”> <complexContent> <extensionbase=“cid:UserSensorPreferenceBaseType”/> </complexContent></complexType>

A temperature sensor type is a tool for describing the sensor adaptationpreference related to the temperature sensor.

A temperature sensor capability type may include sensor adaptationpreference base attributes related to the temperature sensor.

The sensor adaptation preference base attributes related to thetemperature sensor may include a maximum value, a minimum value, and anumber of levels.

The maximum value denotes a maximum value of a user preference relatedto temperature information measured by the temperature sensor.

The minimum value denotes a minimum value of the user preference relatedto the temperature information measured by the temperature sensor.

The number of levels denotes a number of levels of the user preferencewith respect to the temperature information measured by the temperaturesensor.

Source 25 denotes a sensor adaptation preference related to a humiditysensor using the XML. However, a program source shown in Source 25 isonly an example embodiment and does not limit the present disclosure.

[Source 25] <!-- ################################################ --><!-- Humidity Sensor Preference type    --> <!--################################################ --> <complexTypename=“HumiditySensorPrefType”> <complexContent> <extensionbase=“cid:UserSensorPreferenceBaseType”/> </complexContent></complexType>

A humidity sensor type is a tool for describing the sensor adaptationpreference related to the humidity sensor.

A humidity sensor capability type may include sensor adaptationpreference base attributes related to the humidity sensor.

The sensor adaptation preference base attributes related to the humiditysensor may include a maximum value, a minimum value, and a number oflevels.

The maximum value denotes a maximum value of a user preference relatedto humidity information measured by the humidity sensor.

The minimum value denotes a minimum value of the user preference relatedto the humidity information measured by the humidity sensor.

The number of levels denotes a number of levels of the user preferencewith respect to the humidity information measured by the humiditysensor.

Source 26 denotes a sensor adaptation preference related to a lengthsensor using the XML. However, a program source shown in Source 26 isonly an example embodiment and does not limit the present disclosure.

[Source 26] <!-- ################################################ --><!-- Length Sensor Preference type    --> <!--################################################ --> <complexTypename=“LengthSensorPrefType”> <complexContent> <extensionbase=“cid:UserSensorPreferenceBaseType”/> </complexContent></complexType>

A length sensor type is a tool for describing the sensor adaptationpreference related to the length sensor.

A length sensor capability type may include sensor adaptation preferencebase attributes related to the length sensor.

The sensor adaptation preference base attributes related to the lengthsensor may include a maximum value, a minimum value, and a number oflevels.

The maximum value denotes a maximum value of a user preference relatedto length information measured by the length sensor.

The minimum value denotes a minimum value of the user preference relatedto the length information measured by the length sensor.

The number of levels denotes a number of levels of the user preferencewith respect to the length information measured by the length sensor.

Source 27 denotes a sensor adaptation preference related to a motionsensor using the XML. However, a program source shown in Source 27 isonly an example embodiment and does not limit the present disclosure.

[Source 27] <!-- ################################################ --><!- Motion Sensor Preference type     --> <!--################################################ -->   <complexTypename=“MotionSensorPrefType”>     <sequence>     <elementname=“positionpreference” type=“cid:PositionSensorPrefType”minOccurs=“0”/>     <element name=“orientationpreference”type=“cid:OrientationSensorPrefType” minOccurs=“0”/>     <elementname=“velocitypreference” type=“cid:VelocitySensorPrefType”minOccurs=“0”/>     <element name=“angularvelocitypreference”type=“cid:AngularVelocitySensorPrefType” minOccurs=“0”/>     <elementname=“accelerationpreference” type=“cid:AccelerationSensorPrefType”minOccurs=“0”/>     <element name=“angularaccelerationpreference”type=“cid:AngularAccelerationSensorPrefType” minOccurs=“0”/>  </sequence>   </complexType>

A motion sensor capability type is a tool for describing the sensoradaptation preference related to the motion sensor.

The motion sensor capability type may include sensor adaptationpreference base attributes related to the motion sensor.

The sensor adaptation preference base attributes related to the motionsensor may include a position preference, a velocity preference, anacceleration preference, an orientation preference, an angular velocitypreference, and an angular acceleration preference.

The position preference denotes a user preference with respect to theposition.

The velocity preference denotes a user preference with respect to thevelocity.

The acceleration preference denotes a user preference with respect tothe acceleration.

The orientation preference denotes a user preference with respect to theorientation.

The angular velocity preference denotes a user preference with respectto the angular velocity.

The angular acceleration preference denotes a user preference withrespect to the angular acceleration.

Source 28 denotes a sensor adaptation preference related to anintelligent camera sensor using the XML. However, a program source shownin Source 28 is only an example embodiment and does not limit thepresent disclosure,

[Source 28] <!-- ################################################ --><!-- Intelligent Camera Preference Type           --> <!--################################################ --> <complexTypename=“IntelligentCameraPreferenceType”>   <complexContent>    <extension base=“cid:SensorAdaptationPreferenceBaseType”>      <sequence>         <element name=“FaceFeatureTrackingOn”type=“boolean” minOccurs=“0”/>         <elementname=“BodyFeatureTrackingOn” type=“boolean” minOccurs=“0”/>        <element name=“FacialExpressionTrackingOn” type=“boolean”minOccurs=“0”/>         <element name=“GestureTrackingOn” type=“boolean”minOccurs=“0”/>         <element name=“FacialFeatureMask”type=“cid:FacialFeatureMaskType”/>         <elementname=“BodyFeatureMask” type=“cid:BodyFeatureMaskType”/>      </sequence>     </extension>   </complexContent> </complexType><complexType name=“FacialFeatureMaskType”>   <sequence>     <elementname=“Eyes” type=“boolean”/> <element name=“Mouth” type=“boolean”/><element name=“Nose” type=“boolean”/> <element name=“Ears”type=“boolean”/>   </sequence> </complexType> <complexTypename=“BodyFeatureMaskType”>   <sequence>     <element name=“Head”type=“boolean”/>     <element name=“Arms” type=“boolean”/> <elementname=“Hands” type=“boolean”/>     <element name=“Legs” type=“boolean”/>    <element name=“Feet” type=“boolean”/> <element name=“MiddleBody”type=“boolean”/>   </sequence> </complexType>

An intelligent camera sensor capability type is a tool for describingthe sensor adaptation preference related to the intelligent camerasensor.

The intelligent camera sensor capability type may include sensoradaptation preference base attributes related to the intelligent camerasensor.

The sensor adaptation preference base attributes related to theintelligent camera sensor may include a face feature tracking on, a bodyfeature tracking on, a facial expression tracking on, a gesture trackingon, a face tracking map, and a body tracking map.

The face feature tracking on denotes information on whether to activatea face feature tracking mode in which an intelligent camera sensortracks features on a face of the user.

The body feature tracking on denotes information on whether to activatea body feature tracking mode in which the intelligent camera sensortracks features on a body of the user.

The facial expression tracking on denotes information on user preferencewith respect to tracking of a facial expression of the user by theintelligent camera sensor.

The gesture tracking on denotes information on user preference withrespect to tracking of a gesture of the user by the intelligent camerasensor.

The face tracking map provides a Boolean map related to a face trackingmap type. The Boolean map provides face portions that the user wants totrack. Depending on embodiments, the Boolean map according to the facetracking map type may provide eyes, a mouth, a noise, and ears as theface portions.

The body tracking map provides a Boolean map related to a body trackingmap type. The Boolean map provides body portions that the user wants totrack. Depending on embodiments, the Boolean map according to the bodytracking map type may provide a head, arms, hands, legs, feet, and amiddle body as the body portions.

Source 29 denotes a sensor adaptation preference related to an ambientnoise sensor using the XML. However, a program source shown in Source 29is only an example embodiment and does not limit the present disclosure.

[Source 29] <!-- ################################################ --><!-- Ambient Noise Sensor Preference type   --> <!--################################################ --> <complexTypename=“AmbientNoiseSensorPrefType”> <complexContent> <extensionbase=“cid:UserSensorPreferenceBaseType”/> </complexContent></complexType>

An ambient noise sensor type is a tool for describing the sensoradaptation preference related to the ambient noise sensor.

An ambient noise sensor capability type may include sensor adaptationpreference base attributes related to the ambient noise sensor.

The sensor adaptation preference base attributes related to the ambientnoise sensor may include a maximum value, a minimum value, and a numberof levels.

The maximum value denotes a maximum value of a user preference withrespect to ambient noise information measured by the ambient noisesensor.

The minimum value denotes a minimum value of the user preference withrespect to the ambient noise information measured by the ambient noisesensor.

The number of levels denotes a number of levels of the user preferencewith respect to the ambient noise information measured by the ambientnoise sensor.

Source 30 denotes a sensor adaptation preference related to anatmospheric pressure sensor using the XML. However, a program sourceshown in Source 30 is only an example embodiment and does not limit thepresent disclosure.

[Source 30] <!-- ################################################ --><!-- Atmospheric Pressure Sensor Preference type       --> <!--################################################ --> <complexTypename=“AtmosphericPressureSensorPrefType”> <complexContent> <extensionbase=“cid:UserSensorPreferenceBaseType”/> </complexContent></complexType>

An atmospheric pressure sensor type is a tool for describing the sensoradaptation preference related to the atmospheric pressure sensor.

An atmospheric pressure sensor capability type may include sensoradaptation preference base attributes related to the atmosphericpressure sensor.

The sensor adaptation preference base attributes related to theatmospheric pressure sensor may include a maximum value, a minimumvalue, and a number of levels.

The maximum value denotes a maximum value of a user preference withrespect to atmospheric pressure information measured by the atmosphericpressure sensor.

The minimum value denotes a minimum value of the user preference withrespect to the atmospheric pressure information measured by theatmospheric pressure sensor.

The number of levels denotes a number of levels of the user preferencewith respect to the atmospheric pressure information measured by theatmospheric pressure sensor.

Source 31 denotes a sensor adaptation preference related to a velocitysensor using the XML. However, a program source shown in Source 31 isonly an example embodiment and does not limit the present disclosure.

[Source 31] <!-- ################################################ --><!-- Velocity Sensor Preference type      --> <!--################################################ --> <complexTypename=“VelocitySensorPrefType”> <complexContent> <extensionbase=cid:SensorCapabilityBaseType/> </complexContent> </complexType>

A velocity sensor type is a tool for describing the sensor adaptationpreference related to the velocity sensor.

A velocity sensor capability type may include sensor adaptationpreference base attributes related to the velocity sensor.

The sensor adaptation preference base attributes related to the velocitysensor may include a maximum value, a minimum value, and a number oflevels.

The maximum value denotes a maximum value of a user preference withrespect to velocity information measured by the velocity sensor.

The minimum value denotes a minimum value of the user preference withrespect to the velocity information measured by the velocity sensor.

The number of levels denotes a number of levels of the user preferencewith respect to the velocity information measured by the velocitysensor.

Source 32 denotes a sensor adaptation preference related to an angularvelocity sensor using the XML. However, a program source shown in Source32 is only an example embodiment and does not limit the presentdisclosure.

[Source 32] <!-- ################################################ --><!-Angular Velocity Sensor Preference type      --> <!--################################################ --> <complexTypename=“AngularVelocitySensorPrefType”> <complexContent> <extensionbase=cid:SensorCapabilityBaseType/> </complexContent> </complexType>

An angular velocity sensor type is a tool for describing the sensoradaptation preference related to the angular velocity sensor.

An angular velocity sensor capability type may include sensor adaptationpreference base attributes related to the angular velocity sensor.

The sensor adaptation preference base attributes related to the angularvelocity sensor may include a maximum value, a minimum value, and anumber of levels.

The maximum value denotes a maximum value of a user preference withrespect to angular velocity information measured by the angular velocitysensor.

The minimum value denotes a minimum value of the user preference withrespect to the angular velocity information measured by the angularvelocity sensor.

The number of levels denotes a number of levels of the user preferencewith respect to the angular velocity information measured by the angularvelocity sensor.

Source 33 denotes a sensor adaptation preference related to an angularacceleration sensor using the XML. However, a program source shown inSource 33 is only an example embodiment and does not limit the presentdisclosure.

[Source 33] <!-- ################################################ --><!-- Angular Acceleration Sensor Preference type --> <!--################################################ --> <complexTypename=“AngularAccelerationSensorPrefType”> <complexContent> <extensionbase=cid:SensorCapabilityBaseType/> </complexContent> </complexType>

An angular acceleration sensor type is a tool for describing the sensoradaptation preference related to the angular acceleration sensor.

An angular acceleration sensor capability type may include sensoradaptation preference base attributes related to the angularacceleration sensor.

The sensor adaptation preference base attributes related to the angularacceleration sensor may include a maximum value, a minimum value, and anumber of levels.

The maximum value denotes a maximum value of a user preference withrespect to angular acceleration information measured by the angularacceleration sensor.

The minimum value denotes a minimum value of the user preference withrespect to the angular acceleration information measured by the angularacceleration sensor.

The number of levels denotes a number of levels of the user preferencewith respect to the angular acceleration information measured by theangular acceleration sensor.

Source 34 denotes a sensor adaptation preference related to a forcesensor using the XML. However, a program source shown in Source 34 isonly an example embodiment and does not limit the present disclosure.

[Source 34] <!-- ################################################ --><!-- Force Sensor Preference type Preference type  --> <!--################################################ --> <complexTypename=“ForceSensorPrefType”> <complexContent> <extensionbase=“cid:SensorCapabilityBaseType”> </extension> </complexContent></complexType>

A force sensor type is a tool for describing the sensor adaptationpreference related to the force sensor.

A force sensor capability type may include sensor adaptation preferencebase attributes related to the force sensor.

The sensor adaptation preference base attributes related to the forcesensor may include a maximum value and, a minimum value, and a number oflevels.

The maximum value denotes a maximum value of a user preference withrespect to force information measured by the force sensor.

The minimum value denotes a minimum value of the user preference withrespect to the force information measured by the force sensor.

The number of levels denotes a number of levels of the user preferencewith respect to the force information measured by the force sensor.

Source 35 denotes a sensor adaptation preference related to a torquesensor using the XML. However, a program source shown in Source 35 isonly an example embodiment and does not limit the present disclosure.

[Source 35] <!-- ################################################ --><!-- Torque Sensor Preference type  --> <!--################################################ --> <complexTypename=“ForceSensorPrefType”> <complexContent> <extensionbase=“cid:SensorCapabilityBaseType”> </extension> </complexContent></complexType>

A torque sensor type is a tool for describing the sensor adaptationpreference related to the torque sensor.

A torque sensor capability type may include sensor adaptation preferencebase attributes related to the torque sensor.

The sensor adaptation preference base attributes related to the torquesensor may include a maximum value and, a minimum value, and a number oflevels.

The maximum value denotes a maximum value of a user preference withrespect to torque information measured by the torque sensor.

The minimum value denotes a minimum value of the user preference withrespect to the torque information measured by the torque sensor.

The number of levels denotes a number of levels of the user preferencewith respect to the torque information measured by the torque sensor.

Source 36 denotes a sensor adaptation preference related to a pressuresensor using the XML. However, a program source shown in Source 36 isonly an example embodiment and does not limit the present disclosure.

[Source 36] <!-- ################################################ --><!-- Pressure Sensor Preference type     --> <!--################################################ --> <complexTypename=“PressureSensorPrefType”> <complexContent> <extensionbase=“cid:SensorCapabilityBaseType”> </extension> </complexContent></complexType>

A pressure sensor type is a tool for describing the sensor adaptationpreference related to the pressure sensor.

A pressure sensor capability type may include sensor adaptationpreference base attributes related to the pressure sensor.

The sensor adaptation preference base attributes related to the pressuresensor may include a maximum value and, a minimum value, and a number oflevels.

The maximum value denotes a maximum value of a user preference withrespect to pressure information measured by the pressure sensor.

The minimum value denotes a minimum value of the user preference withrespect to the pressure information measured by the pressure sensor.

The number of levels denotes a number of levels of the user preferencewith respect to the pressure information measured by the pressuresensor.

The virtual world processing apparatus according to the exampleembodiments may include sensed information.

The sensed information denotes information collected by the sensor fromthe real world. The sensed information according to example embodimentsmay be information on a command for controlling the sensor. Depending onembodiments, the sensed information may be a command for controlling thesensor so as to reflect the information on the motion, state, intention,shape, and the like of the user of the real world, measured through thesensor, to the virtual world.

Depending on embodiments, the sensed information may serve as a rootelement for sensed information metadata.

Hereinafter, the sensed information will be described in detail withreference to FIG. 13.

FIG. 13 illustrates a sensed information base type 1000, according toexample embodiments.

Referring to FIG. 13, the sensed information base type 1000 may includesensed information base attributes 1010 and any attributes 1020.

The sensed information base type 1000 may be a topmost type of a basetype that may inherit an individual piece of the sensed information.

The sensed information base attributes 1010 denote a group of attributesfor the commands.

The any attributes 1020 denote a group of additional sensed information.The any attributes 1020 may be unique additional sensed informationapplicable to an arbitrary sensor. The any attributes 1020 may allowscalability for inclusion of attributes other than the base attributes.

Source 37 may include a program denoting a sensed information base typeusing the XML. However, Source 37 is only an example embodiment and doesnot limit the present disclosure.

[Source 37] <!-- ################################################ --><!-- Sensed information base type       --> <!--################################################ --> <complexTypename=“SensedInfoBaseType” abstract=“true”> <attribute name=“id”type=“ID” use=“optional”/> <attributeGroupref=“cid:SensedInfoBaseAttributes”/> <anyAttribute namespace=“##other”processContents=“lax”/> </complexType>

The sensed information base attributes 1010 may include an ID 1011, asensor ID reference 1012, a group ID 1013, a priority 1014, anactivation state 1015, and a linked list 1016.

The ID 1011 denotes ID information for recognizing individual identityof the sensed information collected by the sensor.

The sensor ID reference 1012 denotes information referencing the sensor.That is, the sensor ID reference 1012 may be information referencing anID of the sensor that generates information included in particularsensed information.

The group ID 1013 denotes information for recognizing individualidentity of a multi-sensor structure to which the sensor belongs. Thatis, the group ID 1013 denotes ID information for recognizing individualidentity of a multi-sensor structure to which a particular sensorbelongs.

The priority 1014 denotes information on a priority related to anothersensed information sharing the same point at an adapting time of thesensed information. Depending on embodiments, a value 1 may represent ahighest priority and larger values may indicate lower priorities.

The activation state 1015 denotes information for determining whetherthe sensor is in operation.

The linked list 1016 denotes information on link data for grouping aplurality of sensors. Depending on embodiments, the linked list 1016 maybe information on a multi-sensor structure for grouping the sensors by amethod including reference information on IDs of neighboring sensors.

Depending on embodiments, the sensed information base attributes 1010may further include a value, a timestamp, and a life span.

The value denotes a measured value of the sensor. The value may bereceived from the sensor.

The timestamp denotes information on a sensing time of the sensor.

The life span denotes information on a valid period of a sensor command.Depending on embodiments, the life span may be a second unit.

The sensed information base attributes may be rearranged as shown inTable 5.

TABLE 5 Name Definition ID 1011 Individual identity of sensorsensorIdRef 1012 References a sensor that has generated the informationincluded in this specific sensed information. groupID 1013 Identifierfor a group multi-sensor structure to which this specific sensorbelongs. Priority 1014 Describes the priority for sensed informationwith respect to other sensed information in the same group of sensorssharing the same point in time when the sensed information becomeadapted. A value of one indicates the highest priority and larger valuesindicate lower priorities. Activate 1015 whether the effect shall beactivated. a value of true means the effect shall be activated and falsemeans the effect shall be deactivated. Value the value of the effect inpercentage according to the max scale defined within the semanticsdefinition of the individual effects. Linked list 1016 grouping sensorstructure that consists of a group of sensors such that in each recordthere is a field that contains a reference (id) to the next sensor. Timestamp information on a sensing time of the sensor Life span informationon a valid period of a sensor command (expressed with reference to thetimestamp in units of second)

Hereinafter, the sensed information of the sensor will be described inrelation to specific embodiments.

Source 38 denotes sensed information related to a position sensor usingthe XML. However, a program source shown in Source 38 is only an exampleembodiment and does not limit the present disclosure.

[Source 38] <!--#################################### --> <!--Definitionof Position Sensor type --> <!--#################################### --><complexType name=“PositionSensorType”>   <complexContent>    <extension base=“cid:SensedInfoBaseType”>       <sequence>        <element name=“position” type=“cid:PositionValueType”minOccurs=“0”/>       </sequence>       <attribute name=“timestamp”type=“float”       use=“optional”/>       <attribute name=“lifespan”type=“float” use=“optional”/>     </extension>   </complexContent></complexType> <complexType name=“PositionValueType”>   <sequence>    <element name=“Px” type=“float”/>     <element name=“Py”type=“float”/>     <element name=“Pz” type=“float”/>   </sequence></complexType>

A position sensor type is a tool for describing sensed informationrelated to the position sensor.

The position sensor type may include attributes such as a timestamp, alife span, a position, a position value type, Px, Py, and Pz.

The timestamp denotes information on a sensing time of the positionsensor.

The life span denotes information on a valid period of a command of theposition sensor. For example, the life span may be in a unit of seconds.

The position denotes information on a 3-dimensional (3D) value of theposition sensor, expressed by a unit of distance, for example, a meter.

The position value type denotes a tool for indicating a 3D positionvector.

The Px denotes information on an x-axis value of the position sensor.

The Py denotes information on a y-axis value of the position sensor.

The Pz denotes information on a z-axis value of the position sensor.

Source 39 denotes sensed information related to an orientation sensorusing the XML. However, a program source shown in Source 39 is only anexample embodiment and does not limit the present disclosure.

[Source 39] <!--#################################### --> <!--Definitionof Orientation Sensor type --> <!--####################################--> <complexType name=“OrientationSensorType”>   <complexContent>    <extension base=“cid:SensedInfoBaseType”>       <sequence>        <element name=“orientation” type=“cid:OrientationValueType”minOccurs=“0”/>       </sequence>       <attribute name=“timestamp”type=“float”       use=“optional”/>       <attribute name=“lifespan”type=“float” use=“optional”/>     </extension>   </complexContent></complexType> <complexType name=“OrientationValueType”>   <sequence>    <element name=“Ox” type=“float”/>     <element name=“Oy”type=“float”/>     <element name=“Oz” type=“float”/>   </sequence></complexType>

An orientation sensor type is a tool for describing sensed informationrelated to the orientation sensor.

The orientation sensor type may include attributes such as a timestamp,a life span, an orientation, an orientation value type, Ox, Oy, and Oz.

The timestamp denotes information on a sensing time of the orientationsensor.

The life span denotes information on a valid period of a command of theorientation sensor. For example, the life span may be in a unit ofseconds.

The orientation denotes information on a 3D value of the orientationsensor, expressed by a unit of orientation, for example, radians.

The orientation value type denotes a tool for indicating a 3Dorientation vector.

The Ox denotes information on a value of an x-axis rotation angle of theorientation sensor.

The Oy denotes information on a value of a y-axis rotation angle of theorientation sensor.

The Oz denotes information on a value of a z-axis rotation angle of theorientation sensor.

Source 40 denotes sensed information related to an acceleration sensorusing the XML. However, a program source shown in Source 40 is only anexample embodiment and does not limit the present disclosure.

[Source 40] <!--#################################### --> <!--Definitionof Acceleration Sensor type --> <!--####################################--> <complexType name=“AccelerationSensorType”>   <complexContent>    <extension base=“cid:SensedInfoBaseType”>       <sequence>        <element name=“acceleration” type=“cid:AccelerationValueType”minOccurs=“0”/>       </sequence>       <attribute name=“timestamp”type=“float”       use=“optional”/>       <attribute name=“lifespan”type=“float” use=“optional”/>     </extension>   </complexContent></complexType> <complexType name=“AccelerationValueType”>   <sequence>    <element name=“Ax” type=“float”/>     <element name=“Ay”type=“float”/>     <element name=“Az” type=“float”/>   </sequence></complexType>

An acceleration sensor type is a tool for describing sensed informationrelated to the acceleration sensor.

The acceleration sensor type may include attributes, such as, atimestamp, a life span, an acceleration, and an acceleration value type,Ax, Ay, and Az.

The timestamp denotes information on a sensing time of the accelerationsensor.

The life span denotes information on a valid period of a command of theacceleration sensor. For example, the life span may be a unit ofseconds.

The acceleration denotes information on a value of the accelerationsensor, expressed by a unit of acceleration, for example, m/s².

The acceleration value type denotes a tool for indicating a 3Dacceleration vector.

The Ax denotes information on an x-axis value of the accelerationsensor.

The Ay denotes information on a y-axis value of the acceleration sensor.

The Az denotes information on a z-axis value of the acceleration sensor.

Source 41 denotes sensed information related to a light sensor using theXML. However, a program source shown in Source 41 is only an exampleembodiment and does not limit the present disclosure.

[Source 41] <!--#################################### --> <!--Definitionof Light Sensor type --> <!--#################################### --><complexType name=“LightSensorType”>   <complexContent>     <extensionbase=“cid:SensedInfoBaseType”>       <attribute name=“timestamp”type=“float”       use=“optional”/>       <attribute name=“lifespan”type=“float” use=“optional”/> <attribute name=“color”type=“cid:colorType” use=“optional”/>     </extension>  </complexContent> </complexType>

A light sensor type is a tool for describing sensed information relatedto the light sensor.

The light sensor type may include attributes such as a timestamp, a lifespan, a value, and a color.

The timestamp denotes information on a sensing time of the light sensor.

The lifespan denotes information on a valid period of a command of thelight sensor. For example, the life span may be a second unit.

The value denotes information on a light sensor value expressed by aunit of light intensity, for example, LUX.

The color denotes a color that may be provided by the light sensor. Forexample, the color may be an RGB color value.

Source 42 denotes sensed information related to a sound sensor using theXML. However, a program source shown in Source 42 is only an exampleembodiment and does not limit the present disclosure.

[Source 42] <!--######################## --> <!-- SCmd Sound Sensortype  --> <!--######################## --> <complexTypename=“SoundSensorType”>  <complexContent>   <extension base=“cid:SCmdBaseType”/>  </complexContent> </complexType>

A sound sensor command type is a tool for describing sensed informationrelated to the sound sensor.

Source 43 denotes sensed information related to a temperature sensorusing the XML. However, a program source shown in Source 43 is only anexample embodiment and does not limit the present disclosure.

[Source 43] <!--#################################### --> <!--Definitionof Temperature Sensor type --> <!--####################################--> <complexType name=“TemperatureSensorType”>   <complexContent>    <extension base=“cid:SensedInfoBaseType”>       <attributename=“timestamp” type=“float” use=       “optional”/>       <attributename=“lifespan” type=“float” use=“optional”/>     </extension>  </complexContent> </complexType>

A temperature sensor type is a tool for describing sensed informationrelated to the temperature sensor.

The temperature sensor type may include attributes such as a timestamp,a life span, and a value.

The timestamp denotes information on a sensing time of the temperaturesensor.

The life span denotes information on a valid period of a command of thetemperature sensor. For example, the life span may be in a unit orseconds.

The value denotes information on a temperature sensor value expressed bya unit of temperature, for example, ° C. and ° F.

Source 44 denotes sensed information related to a humidity sensor usingthe XML. However, a program source shown in Source 44 is only an exampleembodiment and does not limit the present disclosure.

[Source 44] <!--#################################### --> <!--Definitionof Humidity Sensor type --> <!--#################################### --><complexType name=“HumiditySensorType”>   <complexContent>    <extension base=“cid:SensedInfoBaseType”>       <attributename=“timestamp” type=“float” use=       “optional”/>       <attributename=“lifespan” type=“float” use=“optional”/>     </extension>  </complexContent> </complexType>

A humidity sensor type is a tool for describing sensed informationrelated to the humidity sensor.

The humidity sensor type may include attributes such as a timestamp, alife span, and a value.

The timestamp denotes information on a sensing time of the humiditysensor.

The life span denotes information on a valid period of a command of thehumidity sensor. For example, the life span may be in a unit of seconds.

The value denotes information on a humidity sensor value expressed by aunit of humidity, for example, %.

Source 45 denotes sensed information related to a length sensor usingthe XML. However, a program source shown in Source 45 is only an exampleembodiment and does not limit the present disclosure.

[Source 45] <!--#################################### --> <!--Definitionof Length Sensor type --> <!--#################################### --><complexType name=“LengthSensorType”>   <complexContent>     <extensionbase=“cid:SensedInfoBaseType”>       <attribute name=“timestamp”type=“float” use=       “optional”/>       <attribute name=“lifespan”type=“float” use=“optional”/>     </extension>   </complexContent></complexType>

A length sensor type is a tool for describing sensed information relatedto the length sensor.

The length sensor type may include attributes such as a timestamp, alife span, and a value.

The timestamp denotes information on a sensing time of the lengthsensor.

The life span denotes information on a valid period of a command of thelength sensor. For example, the life span may be in a unit of seconds.

The value denotes information on a length sensor value expressed by aunit of length, for example, meters.

Source 46 denotes sensed information related to a length sensor usingthe XML. However, a program source shown in Source 46 is only an exampleembodiment and does not limit the present disclosure.

[Source 46] <!-- ################################################ --><!-- Definition of Motion Sensor Type   --> <!--################################################ -->   <complexTypename=“MotionSensorType”>     <sequence>       <element name=“position”type= “cid:PositionSensorType” minOccurs=“0”/>       <elementname=“orientation” type= “cid:OrienationSensorType” minOccurs=“0”/>      <element name=“velocity” type= “cid:VelocitySensorType”minOccurs=“0”/>       <element name=“angularvelocity”type=“cid:AngularVelocitySensorType” minOccurs=“0”/>       <elementname=“acceleration” type=“cid:AccelerationSensorType” minOccurs=“0”/>      <element name=“angularacceleration”type=“cid:AngularAccelerationSensorType” minOccurs=“0”/>     </sequence>    <attribute name=“id” type=“ID” use=“optional”/>     <attributename=“idref” type=“IDREF” use=“optional”/>   </complexType>

A motion sensor type is a tool for describing sensed information relatedto the length sensor.

The motion sensor type may include attributes such as an ID, an IDreference, a position, a velocity, an acceleration, an orientation, anangular velocity, and an angular acceleration.

The ID denotes ID information for recognizing individual identity of themotion sensor.

The ID reference denotes additional information related to the ID, theadditional information for recognizing individual identity of the motionsensor.

The position denotes information on a position vector value of a unit ofposition, for example, meters.

The velocity denotes information on a velocity vector value of a unit ofvelocity, for example, m/s.

The acceleration denotes information on an acceleration vector value ofa unit of acceleration, for example, m/s².

The orientation denotes information on an orientation vector value of aunit of orientation, for example, radians.

The angular velocity denotes information on an angular velocity vectorvalue of a unit of angular velocity, for example, radians/s.

The angular acceleration denotes information on an angular accelerationvector value of a unit of angular acceleration, for example, radians/s².

Source 47 denotes sensed information related to an intelligent camerasensor using the XML. However, a program source shown in Source 47 isonly an example embodiment and does not limit the present disclosure.

[Source 47] <!-- ################################################ --><!-- Definition of Intelligent Camera Type   --> <!--################################################ --> <complexTypename=“IntelligentCameraType”>   <complexContent>     <extensionbase=“cid:SensorCommandBaseType”>       <sequence>         <elementname=“FacialAnimationID” type=“IDREF” minOccurs=“0”/> <elementname=“BodyAnimationID” type=“IDREF” minOccurs=“0”/>         <elementname=“FaceFeature” type= “cid:PositionValue” minOccurs=“0”maxOccurs=“255”/>         <element name=“BodyFeature” type=“cid:PositionValue” minOccurs=“0” maxOccurs=“255”/>       </sequence>    </extension>     <attribute name=“timestamp” type=“float”use=“optional”/>     <attribute name=“lifespan” type=“float”use=“optional”/>   </complexContent> </complexType>

An intelligent camera sensor type is a tool for describing sensedinformation related to the intelligent camera sensor.

The intelligent camera sensor type may include a facial animation ID, abody animation ID, a face feature, and a body feature.

The facial animation ID denotes an ID referencing an animation clip withrespect to a facial expression.

The body animation ID denotes an ID referencing an animation clip withrespect to a body.

The face feature denotes information on a 3D position of each facefeature sensed by the intelligent camera sensor.

The body feature denotes information on a 3D position of each bodyfeature sensed by the intelligent camera sensor.

Source 48 denotes sensed information related to an ambient noise sensorusing the XML. However, a program source shown in Source 48 is only anexample embodiment and does not limit the present disclosure.

[Source 48] <!--#################################### --> <!--Definitionof Ambient Noise Sensor type --><!--#################################### --> <complexTypename=“AmbientNoiseSensorType”> <complexContent> <extensionbase=“cid:SensedInfoBaseType”> <attribute name=“timestamp” type=“float”use=“optional”/> <attribute name=“lifespan” type=“float”use=“optional”/> </extension> </complexContent> </complexType>

An ambient noise sensor type is a tool for describing sensed informationrelated to the ambient noise sensor.

The ambient noise sensor type may include attributes such as atimestamp, a life span, and a value.

The timestamp denotes information on a sensing time of the ambient noisesensor.

The life span denotes information on a valid period of a command of theambient noise sensor. For example, the life span may be in a unit ofseconds.

The value denotes information on an ambient noise sensor value expressedby a unit of sound intensity, for example, dBs.

Source 49 denotes sensed information related to an atmospheric pressuresensor using the XML. However, a program source shown in Source 49 isonly an example embodiment and does not limit the present disclosure.

[Source 49] <!--#################################### --> <!--Definitionof Atmospheric Pressure Sensor type --><!--#################################### --> <complexTypename=“AtmosphericPressureSensorType”> <complexContent> <extensionbase=“cid:SensedInfoBaseType”> <attribute name=“timestamp” type=“float”use=“optional”/> <attribute name=“lifespan” type=“float”use=“optional”/> </extension> </complexContent> </complexType>

An atmospheric pressure sensor type is a tool for describing sensedinformation related to the atmospheric pressure sensor.

The atmospheric pressure sensor type may include attributes such as atimestamp, a life span, and a value.

The timestamp denotes information on a sensing time of the atmosphericpressure sensor.

The life span denotes information on a valid period of a command of theatmospheric pressure sensor. For example, the life span may be in a unitof seconds.

The value denotes information on an atmospheric pressure sensor valueexpressed by a unit of atmospheric pressure, for example, a hPa.

Source 50 denotes sensed information related to a velocity sensor usingthe XML. However, a program source shown in Source 50 is only an exampleembodiment and does not limit the present disclosure.

[Source 50] <!--#################################### --> <!--Definitionof Velocity Sensor type --> <!--#################################### --><complexType name=“VelocitySensorType”> <complexContent> <extensionbase=“cid:SensedInfoBaseType”> <sequence> <element name=“velocity”type=“cid:VelocityValueType” minOccurs= “0”/> </sequence> <attributename=“timestamp” type=“float” use=“optional”/> <attributename=“lifespan” type=“float” use=“optional”/> </extension></complexContent> </complexType> <complexType name=“VelocityValueType”><sequence> <element name=“Vx” type=“float”/> <element name=“Vy”type=“float”/> <element name=“Vz” type=“float” minOccurs=“0”/></sequence> </complexType>

A velocity sensor type is a tool for describing sensed informationrelated to the velocity sensor.

The velocity sensor type may include attributes such as a timestamp, alife span, a velocity, a velocity value type, Vx, Vy, and Vz.

The timestamp denotes information on a sensing time of the velocitysensor.

The life span denotes information on a valid period of a command of thevelocity sensor. For example, the life span may be in a unit of seconds.

The velocity denotes information on a velocity sensor value expressed bya unit of velocity, for example, m/s.

The velocity value type denotes a tool for indicating a 3D velocityvector.

The Vx denotes information on an x-axis value of the velocity sensor.

The Vy denotes information on a y-axis value of the velocity sensor.

The Vz denotes information on a z-axis value of the velocity sensor.

Source 51 denotes sensed information related to an angular velocitysensor using the XML. However, a program source shown in Source 51 isonly an example embodiment and does not limit the present disclosure.

[Source 51] <!--#################################### --> <!--Definitionof Angular Velocity Sensor type --><!--#################################### --> <complexTypename=“AngularVelocitySensorType”> <complexContent> <extensionbase=“cid:SensedInfoBaseType”> <sequence> <elementname=“angularvelocity” type=“cid:AngularVelocityValueType”minOccurs=“0”/> </sequence> <attribute name=“timestamp” type=“float”use=“optional”/> <attribute name=“lifespan” type=“float”use=“optional”/> </extension> </complexContent> </complexType><complexType name=“AngularVelocityValueType”> <sequence> <elementname=“AVx” type=“float”/> <element name=“AVy” type=“float”/> <elementname=“AVz” type=“float”/> </sequence> </cofmplexType>

An angular velocity sensor type is a tool for describing sensedinformation related to the angular velocity sensor.

The angular velocity sensor type may include attributes such as atimestamp, a life span, an angular velocity, an angular velocity valuetype, AVx, AVy, and AVz.

The timestamp denotes information on a sensing time of the angularvelocity sensor.

The life span denotes information on a valid period of a command of theangular velocity sensor. For example, the life span may be in a unit ofseconds.

The angular velocity denotes information on an angular velocity sensorvalue expressed by a unit of angular velocity, for example, radians.

The angular velocity value type denotes a tool for indicating a 3Dangular velocity vector.

The AVx denotes information on a value of an x-axis rotation angularvelocity of the angular velocity sensor.

The AVy denotes information on a value of a y-axis rotation angularvelocity of the angular velocity sensor.

The AVz denotes information on a value of a z-axis rotation angularvelocity of the angular velocity sensor.

Source 52 denotes sensed information related to an angular accelerationsensor using the XML. However, a program source shown in Source 52 isonly an example embodiment and does not limit the present disclosure.

[Source 52] <!--#################################### --> <!--Definitionof Angular Acceleration Sensor type --><!--#################################### --> <complexTypename=“AngularAccelerationSensorType”> <complexContent> <extensionbase=“cid:SensedInfoBaseType”> <sequence> <elementname=“angularacceleration” type= “cid:AngularAccelerationValueType”minOccurs=“0”/> </sequence> <attribute name=“timestamp” type=“float”use=“optional”/> <attribute name=“lifespan” type=“float”use=“optional”/> </extension> </complexContent> </complexType><complexType name=“AngularAccelerationValueType”> <sequence> <elementname=“AAx” type=“float”/> <element name=“AAy” type=“float”/> <elementname=“AAz” type=“float”/> </sequence> </complexType>

An angular acceleration sensor type is a tool for describing sensedinformation related to the angular acceleration sensor.

The angular acceleration sensor type may include attributes such as atimestamp, a life span, an angular acceleration, an angular accelerationvalue type, an AAx, an AAy, and an AAz.

The timestamp denotes information on a sensing time of the angularacceleration sensor.

The life span denotes information on a valid period of a command of theangular acceleration sensor. For example, the life span may be in a unitof seconds.

The angular acceleration denotes information on an angular accelerationsensor value expressed by a unit of angular acceleration, for example,radian/s².

The angular acceleration value type denotes a tool for indicating a 3Dangular acceleration vector.

The AAx denotes information on an x-axis value of the angularacceleration sensor.

The My denotes information on a y-axis value of the angular accelerationsensor.

The AAz denotes information on a z-axis value of the angularacceleration sensor.

Source 53 denotes sensed information related to a force sensor using theXML. However, a program source shown in Source 53 is only an exampleembodiment and does not limit the present disclosure.

[Source 53] <!--#################################### --> <!--Definitionof Force Sensor type --> <!--#################################### --><complexType name=“ForceSensorType”> <complexContent> <extensionbase=“cid:SensedInfoBaseType”> <sequence> <element name=“force”type=“cid:ForceValueType” minOccurs=“0”/> </sequence> <attributename=“timestamp” type=“float” use=“optional”/> <attributename=“lifespan” type=“float” use=“optional”/> </extension></complexContent> </complexType> <complexType name=“ ForceValueType”><sequence> <element name=“FSx” type=“float”/> <element name=“FSy”type=“float”/> <element name=“FSz” type=“float”/> </sequence></complexType>

A force sensor type is a tool for describing sensed information relatedto the force sensor.

The force sensor type may include attributes such as a timestamp, a lifespan, a force, a force value type, FSx, FSy, and FSz.

The timestamp denotes information on a sensing time of the force sensor.

The life span denotes information on a valid period of a command of theforce sensor. For example, the life span may be in a unit of seconds.

The force denotes information on a force sensor value expressed by aunit of force, for example, N.

The force value type denotes a tool for indicating a 3D force vector.

The FSx denotes information on an x-axis force value of the forcesensor.

The FSy denotes information on a y-axis force value of the force sensor.

The FSz denotes information on a z-axis force value of the force sensor.

Source 54 denotes sensed information related to a torque sensor usingthe XML. However, a program source shown in Source 54 is only an exampleembodiment and does not limit the present disclosure.

[Source 54] <!--#################################### --> <!--Definitionof Torque Sensor type --> <!--#################################### --><complexType name=“TorqueSensorType”> <complexContent> <extensionbase=“cid:SensedInfoBaseType”> <sequence> <element name=“torque”type=“cid:TorqueValueType” minOccurs=“0”/> </sequence> <attributename=“timestamp” type=“float” use=“optional”/> <attributename=“lifespan” type=“float” use=“optional”/> </extension></complexContent> </complexType> <complexType name=“TorqueValueType”><sequence> <element name=“TSx” type=“float”/> <element name=“TSy”type=“float”/> <element name=“TSz” type=“float”/> </sequence></complexType>

A torque sensor type is a tool for describing sensed information relatedto the torque sensor.

The torque sensor type may include attributes such as a timestamp, alife span, a torque, a torque value type, TSx, TSy, and TSz.

The timestamp denotes information on a sensing time of the torquesensor.

The life span denotes information on a valid period of a command of thetorque sensor. For example, the life span may be in a unit of seconds.

The torque denotes information on a torque sensor value expressed by aunit of torque, for example, N-mm.

The torque value type denotes a tool for indicating a 3D torque vector.

The TSx denotes information on an x-axis torque value of the torquesensor.

The TSy denotes information on a y-axis torque value of the torquesensor.

The TSz denotes information on a z-axis torque value of the forcesensor.

Source 55 denotes sensed information related to a pressure sensor usingthe XML. However, a program source shown in Source 55 is only an exampleembodiment and does not limit the present disclosure.

[Source 55] <!--#################################### --> <!--Definitionof Pressure Sensor type --> <!--#################################### --><complexType name=“PressureSensorType”> <complexContent> <extensionbase=“cid:SensedInfoBaseType”> <attribute name=“timestamp” type=“float”use=“optional”/> <attribute name=“lifespan” type=“float”use=“optional”/> </extension> </complexContent> </complexType>

A pressure sensor type is a tool for describing sensed informationrelated to the pressure sensor.

The pressure sensor type may include attributes such as a timestamp, alife span, and a value.

The timestamp denotes information on a sensing time of the pressuresensor.

The life span denotes information on a valid period of a command of thepressure sensor. For example, the life span may be in a unit of seconds.

The value denotes information on a pressure sensor value expressed by aunit of pressure, for example, N/mm².

FIG. 14 is a flowchart illustrating a virtual world processing methodaccording to example embodiments.

Referring to FIG. 14, the virtual world processing method may store asensor capability related to capability of a sensor in operation S1110.

In operation S1120, a first value received from the sensor may bedetermined based on the sensor capability and a second valuecorresponding to the first value may be transmitted to the virtualworld.

Depending on embodiments, the sensor capability may include a maximumvalue and a minimum value measurable by the sensor. When the first valueis less than or equal to the maximum value and greater than or equal tothe minimum value, the virtual world processing method may transmit thesecond value corresponding to the first value to the virtual world.

Depending on embodiments, the sensor capability may include a unit ofthe first value measured by the sensor. In addition, the sensorcapability may include an offset value added to the first value measuredby the sensor to obtain an absolute value. The sensor capability mayfurther include a number of values measurable by the sensor. The sensorcapability may further include a minimum input value required for thesensor to measure an output value. The sensor capability may furtherinclude an SNR of the sensor. The sensor capability may further includean error of the sensor. Additionally, the sensor capability may furtherinclude a position of the sensor.

The virtual world processing method may further include an operation(not shown) of storing a sensor adaptation preference for manipulationof the first value received from the sensor. The operation oftransmitting the first value may include generating a third value fromthe first value based on the sensor capability and generating the secondvalue from the third value based on the sensor adaptation preference.

Depending on embodiments, the sensor adaptation preference may includeinformation on a method of applying the sensor adaptation preference tothe first value. The sensor adaptation preference may further includeinformation on whether to activate the sensor in the virtual world. Thesensor adaptation preference may further include a unit of the secondvalue used in the virtual world. The sensor adaptation preference mayfurther include a maximum value and a minimum value of the second valueused in the virtual world. In addition, the sensor adaptation preferencemay further include a number of the second values used in the virtualworld.

FIG. 15 illustrates a flowchart of a virtual world processing method,according to other example embodiments.

Referring to FIG. 15, the virtual world processing method may performinitial setting to be input with information of a real world from asensor in operation S1210. Depending on embodiments, the initial settingmay be an operation of activating the sensor.

The virtual world processing method may store a sensor capability asinformation on capability of the sensor and a sensor adaptationpreference as information for manipulation of a value received from thesensor, in operation S1220.

The virtual world processing method may measure information on a motion,state, intention, shape, and the like of a user of the real worldthrough the sensor, in operation S1230. When the sensor is incapable ofmeasuring the information, operation S1230 may be repeated until theinformation is measured.

When the information is measured through the sensor, preprocessing withrespect to the information may be performed in operation S1240.

In addition, the virtual world processing method may control the sensorusing sensed information which is a command for controlling the sensorin operation S1250.

An adaptation RV may determine a first value received from the sensorbased on the sensor capability and transmit a second value correspondingto the first value to a virtual world, in operation S1260, Depending onembodiments, a third value may be generated from the first value basedon the sensor capability, the second value may be generated from thethird value based on the sensor adaptation preference, and the secondvalue may be transmitted to the virtual world.

Hereinafter, a virtual world processing method according to still otherexample embodiments will be described.

The virtual world processing method may collect information on a shapeof a user of a real world using an intelligent camera sensor.

The information on the shape of the user may include information on atleast one of a face, a facial expression, a body movement, and a bodyshape of the user of the real world.

The intelligent camera sensor may sense the information on the shape ofthe user of the real world, and transmit sensed information to a virtualworld processing apparatus. Here, the virtual world processing methodmay collect the information on the shape of the user, sensed by aposition sensor.

The virtual world processing method may perform adaptation of thecollected information with respect to the virtual world, based on asensor capability of the intelligent camera sensor.

The sensor capability related to the intelligent camera sensor mayinclude at least one selected from a feature tracking status, anexpression tracking status, a body movement tracking status, a maximumbody feature point, a maximum face feature point, a tracked feature,tracked facial feature points, tracked body feature points, a featuretype, a facial feature mask, and a body feature mask.

The virtual world processing method may further include storing a sensoradaptation preference for manipulation of the collected information.

In this case, the virtual world processing method may perform adaptationof the collected information with respect to the virtual world, based onthe sensor capability and the sensor adaptation preference. The sensoradaptation preference will be described in detail with reference toFIGS. 10 to 12.

According to example embodiments, the sensor adaptation preference mayinclude at least one selected from a face feature tracking on, a bodyfeature tracking on, a facial expression tracking on, a gesture trackingon, a face tracking map, and a body tracking map.

FIG. 16 illustrates an operation of using a virtual world processingapparatus, according to example embodiments.

Referring to FIG. 16, a user 1310 of a real world may input his or herintention through a sensor 1301. Depending on embodiments, the sensor1301 may include a motion sensor configured to measure a motion of theuser 1310 of the real world, and remote pointers attached to ends ofarms and legs of the user 1310 and configured to measure directions andpositions indicated by the ends of the arms and legs.

A sensor signal may be transmitted to the virtual world processingapparatus, the sensor signal which includes CI 1302 related to an armopening motion, a still standing state, positions of hands and feet, anopen angle of a hand, and the like of the user 1310.

Depending on embodiments, the CI 1302 may include a sensor capability, asensor adaptation preference, and sensed information.

Depending on embodiments, the CI 1302 may include position informationof the arms and the legs of the user 1310, expressed by X_(real),Y_(real), and Z_(real) denoting values on an x-axis, y-axis, and z-axisand Θ_(Xreal), Θ_(Yreal), and Θ_(Zreal) denoting angles with respect tothe x-axis, y-axis, and z-axis.

The virtual world processing apparatus may include an RV engine 1320.The RV engine 1320 may convert information of the real world toinformation applicable to a virtual world, using the CI 1302 included inthe sensor signal.

Depending on embodiments, the RV engine 1320 may convert VWI 1303 usingthe CI 1302.

The VWI 1303 denotes information on the virtual world. For example, theVWI 1303 may include information on an object of the virtual world orelements constituting the object.

The VWI 1303 may include virtual world object information 1304 andavatar information 1305.

The virtual world object information 1304 denotes information on theobject of the virtual world. The virtual world object information 1304may include an object ID denoting ID information for recognizingidentity of the object of the virtual world, and an object control andscale denoting information for controlling a state, size, and the likeof the object of the virtual world.

Depending on embodiments, the virtual world processing apparatus maycontrol the virtual world object information 1304 and the avatarinformation 1305 by a control command. The control command may includecommands such as generation, disappearance, copy, and the like. Thevirtual world processing apparatus may generate the commands byselecting information to be manipulated from the virtual world objectinformation 1304 and the avatar information 1305, along with the controlcommand, and designating an ID corresponding to the selectedinformation.

Source 56 denotes a method of constructing the control command using anXML. However, a program source shown in Source 56 is only an exampleembodiment and does not limit the present disclosure.

[Source 56] <!-- ################################################ --><!-- Definition of Control command for Avatar and virtual object --><!-- ################################################ --> <complexTypename=“ControlCommand”>   <SimpleContent>     <attribute name=“command”type=“cid:commandType” use=     “required”/>     <attributename=“Object” type=“cid:ObjectType” use=     “required”/>     <attributename=“ObjectID” type=“ID” use=“optional”/>   </SimpleContent></complexType> <simpleType name=“commandType”> <restrictionbase=“string”>  <enumeration value=“Create”/>  <enumerationvalue=“Remove”/>  <enumeration value=“Copy”/> </restriction></simpleType> <simpleType name=“ObjectType”> <restriction base=“string”> <enumeration value=“Avatar”/>  <enumeration value=“VirtualObject”/></restriction> </simpleType>

The RV engine 1320 may convert the VWI 1303 by applying information onthe arm opening motion, the still standing state, the positions of handsand feet, the open angle of a hand, and the like, using the CI 1302.

The RV engine 1320 may transmit information 1306 on the converted VWI tothe virtual world. The information 1306 on the converted VWI may includeposition information of arms and legs of an avatar of the virtual world,expressed by X_(virtual), Y_(virtual), and Z_(virtual) denoting valueson the x-axis, y-axis, and z-axis and Θ_(Xvirtual), Θ_(Yvirtual), andΘ_(Zvirtual) denoting angles with respect to the x-axis, y-axis, andz-axis. In addition, the information 1306 may include information on asize of the object of the virtual world, expressed by ascale(s,d,h)_(virtual) denoting a width value, a height value, and adepth value of the object.

Depending on embodiments, in a virtual world 1330 before transmission ofthe information 1306, the avatar is holding the object. In a virtualworld 1340 after transmission of the information 1306, since the armopening motion, the still standing state, the positions of hands andfeet, the open angle of a hand, and the like, are reflected, the avatarof the virtual world may scale up the object.

That is, when the user 1310 of the real world makes a motion of holdingand enlarging the object, the CI 1302 related to the arm opening motion,the still standing state, the positions of hands and feet, the openangle of a hand, and the like, may be generated through the sensor 1301.In addition, the RV engine 1320 may convert the CI 1302 related to theuser 1310 of the virtual world, which is data measured in the realworld, to the information applicable to the virtual world. The convertedinformation may be applied to a structure of information related to theavatar and the object of the virtual world. Therefore, the motion ofholding and enlarging the object may be reflected to the avatar, and theobject may be enlarged.

Example embodiments include computer-readable media including programinstructions to implement various operations embodied by a computer. Themedia may also include, alone or in combination with the programinstructions, data files, data structures, tables, and the like. Themedia and program instructions may be those specially designed andconstructed for the purposes of example embodiments, or they may be ofthe kind well known and available to those having skill in the computersoftware arts. Examples of computer-readable media include magneticmedia such as hard disks, floppy disks, and magnetic tape; optical mediasuch as CD ROM disks; magneto-optical media such as floptical disks; andhardware devices that are specially configured to store and performprogram instructions, such as read-only memory devices (ROM) and randomaccess memory (RAM). Examples of program instructions include bothmachine code, such as produced by a compiler, and files containinghigher level code that may be executed by the computer using aninterpreter. The described hardware devices may be configured to act asone or more software modules in order to perform the operations of theabove-described example embodiments, or vice versa. Examples of themagnetic recording apparatus include a hard disk device (HDD), aflexible disk (FD), and a magnetic tape (MT). Examples of the opticaldisk include a DVD (Digital Versatile Disc), a DVD-RAM, a CD-ROM(Compact Disc-Read Only Memory), and a CD-R (Recordable)/RW.

Further, according to an aspect of the embodiments, any combinations ofthe described features, functions and/or operations can be provided.

Moreover, the virtual world processing apparatus may include at leastone processor to execute at least one of the above-described units andmethods.

Although a few example embodiments have been shown and described, thepresent disclosure is not limited to the described example embodiments.Instead, it would be appreciated by those skilled in the art thatchanges may be made to these example embodiments without departing fromthe principles and spirit of the disclosure, the scope of which isdefined by the claims and their equivalents.

The invention claimed is:
 1. An apparatus for processing a virtualworld, configured to enable interoperability between the virtual worldand a real world, or interoperability between virtual worlds, theapparatus comprising: a sensor configured to sense information of thereal world; and a processor configured to adapt the sensed information,based on sensor capability information comprising a maximum value and aminimum value of a parameter pertaining to the sensor, and a sensoradaptation preference, regarding manipulating the sensed information;wherein the processor is configured to adjust the sensed informationbased on the sensor capability information, wherein in an instancewherein the sensor adaptation preference has a predetermined first valuecorresponding to a strict mode, the processor is configured to directlyapply the adjusted sensed information from the real world to a virtualworld, without manipulation, wherein in an instance wherein the sensoradaptation preference has a predetermined second value corresponding toa scalable mode, the processor is configured to manipulate the adjustedsensed information from the real world, according to the sensoradaptation preference, before applying the adjusted sensed informationto the virtual world; wherein the sensor capability information furthercomprises: a number of levels measurable by the sensor, between themaximum value and the minimum value, a sensitivity representing aminimum limit of an input signal for generating an output signal, and anaccuracy representing a degree of closeness of a measured quantity withrespect to an actual value; and wherein the sensed informationcomprises: group ID information that identifies an individual identityof a multi-sensor structure to which the sensor belongs, sensor IDreference information that identifies the sensor, linked list thatdenotes information on link data for grouping a plurality of sensors,and priority information of another sensed information sharing a samepoint at an adapting time of the sensed information.
 2. The apparatus ofclaim 1, wherein, in an instance wherein the sensor comprises a positionsensor, the sensor capability information comprises at least oneparameter selected from: a range, a range type, an x maximum value, an xminimum value, a y maximum value, a y minimum value, a z maximum value,and a z minimum value of the position sensor.
 3. The apparatus of claim1, wherein, in an instance wherein the sensor comprises an orientationsensor, the sensor capability information comprises at least oneparameter selected from: an orientation range, an orientation rangetype, an x maximum value, an x minimum value, a y maximum value, a yminimum value, a z maximum value, and a z minimum value of theorientation sensor.
 4. The apparatus of claim 1, wherein, in an instancewherein the sensor comprises a velocity sensor, the sensor capabilityinformation comprises at least one parameter selected from: a maximumvalue and a minimum value of the velocity sensor.
 5. The apparatus ofclaim 1, wherein, in an instance wherein the sensor comprises anacceleration sensor, the sensor capability information comprises atleast one parameter selected from: a maximum value and a minimum valueof the acceleration sensor.
 6. The apparatus of claim 1, wherein, in aninstance wherein the sensor comprises an angular velocity sensor, thesensor capability information comprises at least one parameter selectedfrom: a maximum value and a minimum value of the angular velocitysensor.
 7. The apparatus of claim 1, wherein, in an instance wherein thesensor comprises an angular acceleration sensor, the sensor capabilityinformation comprises at least one parameter selected from: a maximumvalue and a minimum value of the angular acceleration sensor.
 8. Theapparatus of claim 1, wherein, in an instance wherein the sensorcomprises a motion sensor, the sensor capability information comprisesat least one parameter selected from: a position capability, a velocitycapability, an acceleration capability, an orientation capability, anangular velocity capability, and an angular acceleration capability. 9.The apparatus of claim 1, wherein, in an instance wherein the sensorcomprises a position sensor, the sensed information comprises at leastone parameter selected from: a timestamp, a position, a unit, a3-dimensional position vector, a position on an x-axis, a position on ay-axis, and a position on a z-axis.
 10. The apparatus of claim 1,wherein, in an instance wherein the sensor comprises a velocity sensor,the sensed information comprises at least one parameter selected from: atimestamp, a velocity, a unit, a 3-dimensional velocity vector, avelocity on an x-axis, a velocity on a y-axis, and a velocity on az-axis.
 11. The apparatus of claim 1, wherein, in an instance whereinthe sensor comprises an acceleration sensor, the sensed informationcomprises at least one parameter selected from: a timestamp, anacceleration, a unit, a 3-dimensional acceleration vector, anacceleration on an x-axis, an acceleration on a y-axis, and anacceleration on a z-axis.
 12. The apparatus of claim 1, wherein, in aninstance wherein the sensor comprises an orientation sensor, the sensedinformation comprises at least one parameter selected from: a timestamp,an orientation, a unit, a 3-dimensional orientation vector, anorientation of an x-axis, an orientation of a y-axis, and an orientationof a z-axis.
 13. The apparatus of claim 1, wherein, in an instancewherein the sensor comprises an angular velocity sensor, the sensedinformation comprises at least one parameter selected from: a timestamp,an angular velocity, a unit, a 3-dimensional angular velocity vector, anangular velocity on an x-axis, an angular velocity on a y-axis, and anangular velocity on a z-axis.
 14. The apparatus of claim 1, wherein, inan instance wherein the sensor comprises an angular acceleration sensor,the sensed information comprises at least one parameter selected from: atimestamp, an angular acceleration, a unit, a 3-dimensional angularacceleration vector, an angular acceleration on an x-axis, an angularacceleration on a y-axis, and an angular acceleration on a z-axis. 15.The apparatus of claim 1, wherein, in an instance wherein the sensorcomprises a motion sensor, the sensed information comprises at least oneparameter selected from: a position, a velocity, an acceleration, anorientation, an angular velocity, and an angular acceleration.
 16. Theapparatus of claim 1, wherein, in an instance wherein the sensorcomprises a position sensor, the sensor adaptation preference comprisesat least one parameter selected from: a range and a number of levels ofthe position sensor.
 17. The apparatus of claim 1, wherein, in aninstance wherein the sensor comprises an orientation sensor, the sensoradaptation preference comprises at least one parameter selected from: anorientation range and a number of levels of the orientation sensor. 18.The apparatus of claim 1, wherein, in an instance wherein the sensorcomprises a velocity sensor, the sensor adaptation preference comprisesat least one parameter selected from: a maximum value, a minimum value,and a number of levels of the velocity sensor.
 19. The apparatus ofclaim 1, wherein, in an instance wherein the sensor comprises anacceleration sensor, the sensor adaptation preference comprises at leastone parameter selected from: a maximum value, a minimum value, and anumber of levels of the acceleration sensor.
 20. The apparatus of claim1, wherein, in an instance wherein the sensor comprises an angularvelocity sensor, the sensor adaptation preference comprises at least oneparameter selected from: a maximum value, a minimum value, and a numberof levels of the angular velocity sensor.
 21. The apparatus of claim 1,wherein, in an instance wherein the sensor comprises an angularacceleration sensor, the sensor adaptation preference comprises at leastone parameter selected from: a maximum value, a minimum value, and anumber of levels of the angular acceleration sensor.
 22. The apparatusof claim 1, wherein, in an instance wherein the sensor comprises amotion sensor, the sensor adaptation preference comprises at least oneparameter selected from: a position preference, a velocity preference,an acceleration preference, an orientation preference, an angularvelocity preference, and an angular acceleration preference.
 23. Theapparatus of claim 1, wherein the sensor comprises an intelligent camerasensor, the sensor capability information comprises at least oneparameter selected from: a feature tracking status, an expressiontracking status, a body movement tracking status, a maximum body featurepoint, a maximum face feature point, a tracked feature, tracked facialfeature points, tracked body feature points, a feature type, a facialfeature mask, and a body feature mask of the intelligent camera sensor.24. The apparatus of claim 1, wherein, in an instance wherein the sensorcomprises an intelligent camera sensor, the sensed information comprisesat least one of: a facial animation ID, a body animation ID, a facefeature, a body feature, and a timestamp.
 25. The apparatus of claim 1,wherein the sensor adaptation preference comprises at least oneparameter selected from: a face feature tracking on, a body featuretracking on, a facial expression tracking on, a gesture tracking on, aface tracking map, and a body tracking map of the intelligent camerasensor.
 26. The apparatus of claim 1, wherein, in an instance whereinthe sensor comprises a light sensor, the sensor capability informationcomprises at least one parameter selected from: a maximum value, aminimum value, a color, and a location of the light sensor.
 27. Theapparatus of claim 1, wherein, in an instance wherein the sensorcomprises an ambient noise sensor, the sensor capability informationcomprises at least one parameter selected from: a maximum value, aminimum value, and a location of the ambient noise sensor.
 28. Theapparatus of claim 1, wherein, in an instance wherein the sensorcomprises a temperature sensor, the sensor capability informationcomprises at least one parameter selected from: a maximum value, aminimum value, and a location of the temperature sensor.
 29. Theapparatus of claim 1, wherein, in an instance wherein the sensorcomprises a humidity sensor, the sensor capability information comprisesat least one parameter selected from: a maximum value, a minimum value,and a location of the humidity sensor.
 30. The apparatus of claim 1,wherein, in an instance wherein the sensor comprises a length sensor,the sensor capability information comprises at least one parameterselected from: a maximum value, a minimum value, and a location of thelength sensor.
 31. The apparatus of claim 1, wherein, in an instancewherein the sensor comprises an atmospheric pressure sensor, the sensorcapability information comprises at least one parameter selected from: amaximum value, a minimum value, and a location of the atmosphericpressure sensor.
 32. The apparatus of claim 1, wherein, in an instancewherein the sensor comprises a force sensor, the sensor capabilityinformation comprises at least one parameter selected from: a maximumvalue and a minimum value of the force sensor.
 33. The apparatus ofclaim 1, wherein, in an instance wherein the sensor comprises a torquesensor, the sensor capability information comprises at least oneparameter selected from: a maximum value, a minimum value, and alocation of the torque sensor.
 34. The apparatus of claim 1, wherein, inan instance wherein the sensor comprises a pressure sensor, the sensorcapability information comprises at least one parameter selected from: amaximum value, a minimum value, and a location of the pressure sensor.35. The apparatus of claim 1, wherein, in an instance wherein the sensorcomprises a sound sensor, the sensor capability information comprises atleast one parameter selected from: a maximum value and a minimum valueof the sound sensor.
 36. The apparatus of claim 1, wherein, in aninstance wherein the sensor comprises a light sensor, the sensedinformation comprises at least one parameter selected from: a timestamp,a value, a unit, and a color of the light sensor.
 37. The apparatus ofclaim 1, wherein, in an instance wherein the sensor comprises an ambientnoise sensor, the sensed information comprises at least one parameterselected from: a timestamp, a lifespan, a unit, and a value of theambient noise sensor.
 38. The apparatus of claim 1, wherein, in aninstance wherein the sensor comprises a temperature sensor, the sensedinformation comprises at least one parameter selected from: a timestamp,a unit, and a value of the temperature sensor.
 39. The apparatus ofclaim 1, wherein, in an instance wherein the sensor comprises a humiditysensor, the sensed information comprises at least one parameter selectedfrom: a timestamp, a unit, and a value of the humidity sensor.
 40. Theapparatus of claim 1, wherein, in an instance wherein the sensorcomprises a length sensor, the sensed information comprises at least oneparameter selected from: a timestamp, a unit, and a value of the lengthsensor.
 41. The apparatus of claim 1, wherein, in an instance whereinthe sensor comprises an atmospheric pressure sensor, the sensedinformation comprises at least one parameter selected from: a timestamp,a unit, and a value of the atmospheric pressure sensor.
 42. Theapparatus of claim 1, wherein, in an instance wherein the sensorcomprises a force sensor, the sensed information comprises at least oneparameter selected from: a timestamp, a force, a unit, a 3D forcevector, a force on an x-axis, a force on a y-axis, and a force on az-axis of the force sensor.
 43. The apparatus of claim 1, wherein, in aninstance wherein the sensor comprises a torque sensor, the sensedinformation comprises at least one parameter selected from: a timestamp,a torque, a unit, a 3D torque vector, a torque on an x-axis, a torque ona y-axis, and a torque on a z-axis of the torque sensor.
 44. Theapparatus of claim 1, wherein, in an instance wherein the sensorcomprises a pressure sensor, the sensed information comprises at leastone parameter selected from: a timestamp, a unit, and a value of thepressure sensor.
 45. The apparatus of claim 1, wherein, in an instancewherein the sensor comprises a sound sensor, the sensed informationcomprises at least one parameter selected from: a maximum value and aminimum value of the sound sensor.
 46. The apparatus of claim 1,wherein, in an instance wherein the sensor comprises a light sensor, thesensor adaptation preference comprises at least one parameter selectedfrom: a maximum value, a minimum value, a number of levels, and anunfavorable color of the light sensor.
 47. The apparatus of claim 1,wherein, in an instance wherein the sensor comprises an ambient noisesensor, the sensor adaptation preference comprises at least oneparameter selected from: a maximum value, a minimum value, and a numberof levels of the ambient noise sensor.
 48. The apparatus of claim 1,wherein, in an instance wherein the sensor comprises a temperaturesensor, the sensor adaptation preference comprises at least oneparameter selected from: a maximum value, a minimum value, and a numberof levels of the temperature sensor.
 49. The apparatus of claim 1,wherein, in an instance wherein the sensor comprises a humidity sensor,the sensor adaptation preference comprises at least one parameterselected from: a maximum value, a minimum value, and a number of levelsof the humidity sensor.
 50. The apparatus of claim 1, wherein, in aninstance wherein the sensor comprises a length sensor, the sensoradaptation preference comprises at least one parameter selected from: amaximum value, a minimum value, and a number of levels of the lengthsensor.
 51. The apparatus of claim 1, wherein, in an instance whereinthe sensor comprises an atmospheric pressure sensor, the sensoradaptation preference comprises at least one parameter selected from: amaximum value, a minimum value, and a number of levels of theatmospheric pressure sensor.
 52. The apparatus of claim 1, wherein, inan instance wherein the sensor comprises a force sensor, the sensoradaptation preference comprises at least one parameter selected from: amaximum value, a minimum value, and a number of levels of the forcesensor.
 53. The apparatus of claim 1, wherein, in an instance whereinthe sensor comprises a torque sensor, the sensor adaptation preferencecomprises at least one parameter selected from: a maximum value, aminimum value, and a number of levels of the torque sensor.
 54. Theapparatus of claim 1, wherein, in an instance wherein the sensorcomprises a pressure sensor, the sensor adaptation preference comprisesat least one parameter selected from: a maximum value, a minimum value,and a number of levels of the pressure sensor.
 55. The apparatus ofclaim 1, wherein, in an instance wherein the sensor comprises a soundsensor, the sensor adaptation preference comprises at least oneparameter selected from: a maximum value and a minimum value of thesound sensor.
 56. The apparatus of claim 1, wherein the processor isconfigured to determine a first value received from the sensor based onthe sensor capability information, and output a second valuecorresponding to the first value, such that the second value is appliedto the virtual world.
 57. The apparatus of claim 1, wherein theprocessor is configured to generate a third value from a first value,based on the sensor capability information; and generate a second valuefrom the third value, based on the sensor adaptation preference.